Closed aubade closed 8 years ago
Unfortunately, this still seems to be an issue in the 1.0.1.v201606011426 release, with the same symptoms. I uninstalled and reinstalled DDT just to make sure it wasn't an issue in my installatian.
(I suspect the fix may just not have gotten baked into the release files)
Oh, run configurations! What happened is that I fixed this for the env vars in Build Target execution, I thought that's where the problem was (and indeed it was buggy there as well). Will fix here as well
Ok, I believe it is fixed now.
When setting per-Run Configuration environment variables, using eclipse substitutions, said substitutions do not appear to be properly resolved, at least on Win32 (I haven't yet tested this on linux or any other platforms yet)
It's pretty easy to illustrate this; create a project with this source file:
Then create a run configuration for it, and in the environment tab, make a variable named
PROJNAME
and set its value to${project_name}
; It should return whatever project is currently active in eclipse at the time you hit the run button, but here it just prints ${project_name}.