Hi there,
I noticed a strange behavior when setting PATH EnvVar with help of the EnvVars Plugin.
I am doing a simple "hello world" kind of program using Allegro 5.0.5 Libray, and set up a very simple project with a single "main.c" and 4 targets (Debug and Release, both and dinamically statically linked to the library).
Compiling and linking is no problem and each target built correctly (and works
)
Still, the dll's to with I dynamically link aren't in the executable path nor in Win7 %PATH%, so I defined a "liballeg" set of a single Envvar (also set to be used in the EnVars tab of project properties) "PATH" with value "%PATH%;pathtoliballegro;pathto mingwruntime libraries" (see attached pictures).
This allows me to run the dynamically linked executables without actually changing PATH in the windows environment
Well, everything works fine until I press "build" (EVEN if the current target is up to date and nothig has tobe done), then the dynamically linked executables fails to start up and the OS is giving the "unable to find dll" error message.
If I go to the envVars panel and press "set now"
or I go in the envVars tab in project properties and set again the (same) set of envvars, then the executables are able to find their dll...
This does not seem the intended behavior, but maybe I am doing something wrog so I am asking if this could be a bug or is only my fault.
I am using the latest official release of C::B (10.05) over Win7, and MinGW 4.5.2 toolchain (NOT the one bundled in C::B).
Images
Thanks for any help