Community
Participate
Working Groups
AS IS: Target platform definition allows us to set available plugins, vm arguments etc. Out of this information, a new instance of Java/Junit launch configuration inherit some settings. Our application relies on jni/native code and different native libraries. Se we can specify LD_LIBRARY_PATH and other environment variables for the Java/JUnit launch configurations but we can NOT specify LD_LIBRARY_PATH etc for the target platform. So every developer creating new launch configuration must manually set LD_LIBRARY_PATH and few other variables to the right values, which is both error prone and highly unreliable. TO BE: It would be great if: 1) the target platform definition file could include environment variables section 2) those environment variables would be automatically re-used by newly created java/JUnit launch configurations (mapAttribute key="org.eclipse.debug.core.environmentVariables") 3) (optional) a nice UI for the target editor allowing me edit environment variables
I see how this would be useful for your application. There isn't committer time available for working on it so I have marked this as help wanted. If this was implemented it should definitely have a UI in the target editor and wizard similar to the environment tab. This could mean copying a lot of the UI code from debug. Alternatively, moving the debug UI into an 'environment block' that could be made API (or x-friended) would allow PDE to reuse it. The API might be useful for other applications as well.
(In reply to comment #1) > If this was implemented it should definitely have a UI in the target editor > and wizard similar to the environment tab. This could mean copying a lot of > the UI code from debug. Alternatively, moving the debug UI into an > 'environment block' that could be made API (or x-friended) would allow PDE > to reuse it. The API might be useful for other applications as well. If someone were to work on this, and were to look at making API from the components on the EnvironmentTab, the relevant classes / methods would be: org.eclipse.debug.ui.EnvironmentTab org.eclipse.debug.core.ILaunchManager#getNativeEnvironment() org.eclipse.debug.core.ILaunchManager.getNativeEnvironmentCasePreserved()
