User forums > Help

%PATH% modified by Code::Blocks

<< < (2/3) > >>

MortenMacFly:

--- Quote from: Folco on September 05, 2011, 04:27:40 pm ---It seems that C::B has removed the entry you added manually.

--- End quote ---
Sorry, but this is impossible. I suspect that this is a general issue: You can verify by instead of running C::B you run a cmd.exe directly. It should be the same there. C::B does not such magic in the backhand.

Some other thoughts:

Under Windows XP if you change the system path a re-start may be required (or at least a log-off and log-on).

Make sure you are running only one instance (a fresh one) of C::B, otherwise the environment of the parent application is used which is not updated automatically if you change it in the settings... as it is with every other Windows application btw..

Make sure you didn't apply a custom path using the envvar plugin of C::B.

Folco:

--- Quote ---otherwise the environment of the parent application is used which is not updated automatically if you change it in the settings
--- End quote ---
You are right !

The instance of C::B which I used was launched with RocketDock ( http://rocketdock.com/ ), and I had the problem.
When I launch C::B using the Start Menu of Windows, it works fine ! So it seems to be a RocketDock problem (which would save an old environment state at installation ???).

Many thanks for your answers and your help. :)


edit -> I confirm that by desinstalling/reinstalling RocketDock, all works fine now. Many thanks again. =)

MortenMacFly:

--- Quote from: Folco on September 05, 2011, 06:08:58 pm ---The instance of C::B which I used was launched with RocketDock ( http://rocketdock.com/ ), and I had the problem.

--- End quote ---
Changes in the environment settings are (by design) never propagated to running applications on Windows. This is a wise thing to do btws. So you'll need either to launch a new fresh application or kill/restart the (parent of a) running application. Sometimes, if services are involved, this won't do it, too. In that case it can be required to restart Windows. To avoid such hassle, the envvar plugin exists in Code::Blocks. This allows you to create and/or change environment variables at runtime, but only within the focus of Code::Blocks and all child applications started by Code::Blocks (like your compiled application).

BTW: It's similar on Linux, so this is not "a Windows thing".

Folco:
Thanks for your tips. :)

oBFusCATed:
Morten:
You're almost write, because the Explorer detects changes to the env
and all started apps from the explorer has the new env.
And there is no need for logout/login, only app restart.

Navigation

[0] Message Index

[#] Next page

[*] Previous page