Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341530 - RFE: Auto-populate LD_LIBRARY_PATH/PATH in launch config for project references
Summary: RFE: Auto-populate LD_LIBRARY_PATH/PATH in launch config for project references
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build-managed (show other bugs)
Version: 7.0.2   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-31 14:19 EDT by Andrew Overholt CLA
Modified: 2020-09-04 15:22 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2011-03-31 14:19:41 EDT 
Consider the following scenario:

- projectA is a managed build library project
- projectB is a managed build executable project which uses projectA's library and has a project reference to projectA

When one creates a launch configuration for projectB, one must manually add an LD_LIBRARY_PATH (or PATH on Windows, I'm told) environment variable that references projectA's build location.  It would be nice if this were done automatically.
Comment 1 James Blackburn CLA 2011-03-31 15:09:31 EDT 
As a more generic request, we need all toolchain environment (or at least an integrator configurable amount of it) to be set before running the debugger.