Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Custom/environment variables

<< < (2/2)

rickg22:
Yiannis, when you say "in CVS", you mean in BOTH branches, right? (crosses fingers  :? )

Also, I suppose these variables are stored in a SEPARATE file, so the .cbp remains unchanged (otherwise, we'd see about 1,000 CVS commits of codeblocks.cbp :lol: )

mandrav:

--- Quote from: rickg22 ---Yiannis, when you say "in CVS", you mean in BOTH branches, right? (crosses fingers  :? )
--- End quote ---

Cross them all you want ;)
Yes, both branches.

--- Quote from: rickg22 ---Also, I suppose these variables are stored in a SEPARATE file, so the .cbp remains unchanged (otherwise, we'd see about 1,000 CVS commits of codeblocks.cbp :lol: )
--- End quote ---

The global (per-compiler) vars are stored in the global C::B configuration (registry for win32).
The per-project and per-target are kept in the project file of course.

Yiannis.

rickg22:
Okay! :) I was just trying to figure out how this would make possible the building of both branches of codeblocks with the same global setup.

David Perfors:

--- Quote from: mandrav ---
--- Quote ---Which variable will have the highest priority?
--- End quote ---

They 're applied in this order: Global -> Project -> Target
so if you set the same variable in global vars and in target vars, target's will be the one last set.
--- End quote ---

It is strange that the Global variables are not overridden by the Project variables :roll:
I tried to compile codeblocks with the cvs projectfile (including WX_DIR var with a path that doesn't excist on my system) It couldn't compile, because the wx/ headers couldn't be found.
I added WX_DIR and WX_CFG to the Global variables and it worked...

Navigation

[0] Message Index

[*] Previous page