hi,
:shock: .. it seems that CB does not relink an application when a linked library has changed.
(can be very annoying: do a change in a lib, build .. look for bug !!! .. oops : CB did not link app !)
Even when the library is another project in the same workspace,
and the main app project has a dependency on the lib, it does not link the app.
kinda funny actually, CB sees the change in the src code of the lib & rebuilds the lib ...
then just ignores the newly built lib & says the app is 'up to date' !! :P
I havent entered this as a bug (yet) ...
maybe I'm missing something somewhere ??
("Libraries used in project" in "Project Options" ?? everything is empty ?)
thx
Philippe
Does the main project have an dependency on the lib project?
Tim S
Quote from: stahta01 on January 02, 2008, 10:24:20 PM
Does the main project have an dependency on the lib project?
Tim S
yes it does.
CB correctly builds the lib through the dependency when I do a build on the main app,
it just doesn't relink the main app.
same thing with an 'external' lib, if it changed, CB will not rebuild the main app.
says : 'up to date'
thank you
I reported the same (or similar) problem here (http://forums.next.codeblocks.org/index.php/topic,7402.msg56310.html#msg56310)
regards,
Wobien
Static libs are a special case which is not handled by the projects inter-dependency mechanism.
You should add the lib as an external dependency for this to work: project->properties->[select target]->external dependencies.
ah !
never noticed that button before !
thank you,
problem solved !
Yes - Thank-you. Problem solved! :D This had been making me miserable for quite some time!