Author Topic: I always have to rebuild the whole workspace...  (Read 4736 times)

skyplus

  • Guest
I always have to rebuild the whole workspace...
« on: November 30, 2007, 04:49:43 am »
In my workspace I have two wxWidgets application projects and several static library projects which work for them.
But comes this problem:
assume they are    libA.cbp, libB.cbp, AppA.cbp and AppB.cbp in root.workspace.

When i have modified a cpp file in libA.cbp, then built it, it generated the new library file. After that, i shall build up a
new Appa.cbp which uses libA.a. But strangely, Appa seems to act like libA.a never changed, or only changed half of
my modification with libA! Even Rebuild Appa.

So, always I had to rebuild the whole workspace to get it right.

Why does this happen? Can setting denpendencies work out this problem?


my codeblocks is svn 4639. Thanks!

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9723
Re: I always have to rebuild the whole workspace...
« Reply #1 on: November 30, 2007, 07:36:02 am »
Why does this happen? Can setting denpendencies work out this problem?
Sure you can - in project settings you can setup project dependencies - thus dependencies of different projects within a workspace. Additionally you can setup for each targets "binary" dependencies - thus the target will be re-compiled (linked) if e.g. an external library is newer. Search the WiKi for more information. It's very well explained there.
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

skyplus

  • Guest
Re: I always have to rebuild the whole workspace...
« Reply #2 on: December 04, 2007, 07:15:57 am »
Why does this happen? Can setting denpendencies work out this problem?
Sure you can - in project settings you can setup project dependencies - thus dependencies of different projects within a workspace. Additionally you can setup for each targets "binary" dependencies - thus the target will be re-compiled (linked) if e.g. an external library is newer. Search the WiKi for more information. It's very well explained there.
With regards, Morten.

Thanks! It is well working now :D