Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: Krox on January 28, 2012, 05:00:03 pm
-
I am currently developing a compiler. So for testing I have a second project, which is compiled with it. Now obviously, it depends on the first compiler-project. But just checking the box in "project's dependencies..." doesn't seem to have an effect at all. Changing the compiler source, and then compiling the testing-project doenst trigger a new compilation of the compiler. What am I missing here? Some clues would be much appreciated.
-
I am guessing you tried project dependencies; it only does build order effect.
Try looking up "external dependencies" on CB and see if that helps.
The version number of Code::Blocks being used matters in this question.
Additional you can ... add an external dependency for the relevant targets of your app in "Properties -> Build targets -> Dependencies -> External dependency files" to the appropriate library.
Tim S.
-
Well, that explains why it doesn't work.
I tried the "external dependencies": This only re-links the project when the depency changes, it doesnt re-compile the source. Furthermore, when building the dependant, it doesn't trigger compilation (when needed) of the dependency. Which seem logical, cause with "external depency" C::B doesn't know, the file (in this case the compiler-binary), origins from another project in the same workspace. So this isn't what I I would like to have. Thanks anyway.
For the time being, the problem isn't critical, as I have only two projects. Just was wondering, how the "project's depencies" work in C::B.
My C::B version is 10.05 (ubuntu repository).