User forums > Using Code::Blocks

Does not recompile changed header files?

<< < (8/8)

ollydbg:
There is some thing off topic, can we use the gcc option "-MF" to generate a dependency file.
Then we can use the dependency file to check whether we need to build some cpp files.
see:
http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Preprocessor-Options.html

Butter-Swimming Butterfly:

--- Quote from: oBFusCATed on June 21, 2012, 05:57:13 pm ---
--- Quote from: carra on June 21, 2012, 05:39:58 pm ---Unfortunately, from a user perspective that is not intuitive. Is this a conscious decision? I always use the same include & library folder, and it would be way more convenient (an maintainable) to just set it once instead of setting it on every project...

--- End quote ---
Yes, but this is considered a bad practice to put something in there.
And I guess this is an optimization for the dependency checking.
As the include/lib search paths are meant for setting paths to SDK which doesn't change often.
C::B has lots of tools to make it easy for the user to setup projects the right way. You can even script it.

--- End quote ---

1. I think the "Global compiler settings > Search directories" tab probably should include a brief note about this issue.
2. I've had trouble similar to what carra and Decrius have experienced. Is it possible to write a script for CodeBlocks somewhere that virtually (transiently) appends additional Compiler Search directories to any project (or source file) being built?

Navigation

[0] Message Index

[*] Previous page

Go to full version