User forums > Using Code::Blocks

Environment variables

<< < (2/2)

MortenMacFly:

--- Quote from: jens on December 08, 2012, 01:37:10 am ---It would possibly work, if it would be possible to ensure EnvVar-plugin sets the path later than the compiler-plugin does.

--- End quote ---
As the envvar exposes its function to scripting, a pre-build step might work, too.

markos:
I just tried that, it didn't work.

As a pre-build step, I did 'export TEST=test:${PATH}' and 'export'. The variable 'TEST' did not appear.

MortenMacFly:

--- Quote from: markos on December 08, 2012, 05:23:58 pm ---I just tried that, it didn't work.

As a pre-build step, I did 'export TEST=test:${PATH}' and 'export'. The variable 'TEST' did not appear.

--- End quote ---
I am not sure if you really tried what I meant, but just to make sure: I didn't mean a "export" statement, but calling a method exposed to scripting from the envvars plugin.

Navigation

[0] Message Index

[*] Previous page