Hi all,
A great feature of C::B is the global variables - I stumbled upon it when messing around with the OGRE projects, so my grasp of the subject may be incomplete.
I can successfully use the hady global variables to direct the compiler and linker to the files required for a project. If I rebuild the entire project everything works as expected, but if I make a change to a header which is pointed to by a global variable the compiler does not rebuild the any of the cpp's which include the modified header.
I'll try to clarify by means of an example:
Supposing we were creating a static library MyLib, and its directory structures looks something like this:
MyLib
+source
+include
+lib
In order for the compiler to compile MyLib we would use MyLibDir in the [Build Options]->[Directories] as follows:
[Build Options]->[Directories]->[Compiler] $(#MyLibDir.include)
If we try building MyLib everything works and links and there's happiness and cheering all around. Until, that is, we start making changes to the header files in MyLib\Include and press the build button. The build simply returns with "Target is up to date. Nothing to be done."
If however we used a relative path (eg. "..\include") in the [Build Options]->[Directories]->[Compiler] settings the project would rebuild and compile as expected.
Am I using global variables incorrectly or is this a bug??
Thanks
Nix