Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367517 - External run configuration doesn't properly set environment variable
Summary: External run configuration doesn't properly set environment variable
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-23 14:00 EST by Josh Davidson CLA
Modified: 2019-09-02 15:12 EDT (History)
1 user (show)

See Also:


Attachments
Screenshot of how things are setup (88.36 KB, image/png)
2011-12-23 14:01 EST, Josh Davidson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Davidson CLA 2011-12-23 14:00:42 EST
Build Identifier: Build id: 20110916-0149

I have a CDT project that has a couple different build configurations.  One produces a shared library and another generates an executable that runs unit test using Google Test.  In order for the unit test executable to run, the location of dll (shared library) needs to be in the PATH environment variable.  I've setup an external run configuration (see screenshots) to execute the unit tests, but it doesn't work.  You'll notice that I used an absolute path for the value I appended to the environment variable.  I had previously tried setting it using workspace_loc.  I also tried replace instead of append.  That also did not work.

So how do I know that it's not setting the path correctly?  Well, if I exit out of eclipse, manually set the PATH environment variable to include the directory in question and relaunch eclipse, the run configuration works as-expected.

Reproducible: Always

Steps to Reproduce:
1. Create an external run configuration that executes a program dependent on a shared library not already in the PATH environment variable
2.  Update the external run configuration to append the location of the shared library PATH environment variable
3.  Attempt to run it
Comment 1 Josh Davidson CLA 2011-12-23 14:01:37 EST
Created attachment 208784 [details]
Screenshot of how things are setup
Comment 2 Josh Davidson CLA 2011-12-23 14:02:20 EST
I should note that I also attempted to run eclipse "as administrator" just in case it was a UAC issue, but that had no effect.
Comment 3 Eclipse Genie CLA 2018-10-02 14:43:13 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Lars Vogel CLA 2019-09-02 14:58:46 EDT
This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
Comment 5 Lars Vogel CLA 2019-09-02 15:12:45 EDT
This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.