Author Topic: Track lib changes ?  (Read 7862 times)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9529
Re: Track lib changes ?
« Reply #15 on: September 10, 2010, 05:57:59 pm »

Ok - so you create two virtual targets in BOTH projects:
One called "Windows", that includes the Windows release/target and OGRE (probably also SFML).
One called "Linux", that includes the Linux release/target and OGRE (probably also SFML).

Then on workspace level you select the target named "Windows". As it is present with exactly the same name  in both projects if you hit "build workspace" the right combination is compiled.

The same applies to Linux. In addition I would set the platform flag for the main projects as needed t avoid compiling what's not supported on the current platform. That's pretty much it.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Kalith

  • Multiple posting newcomer
  • *
  • Posts: 67
Re: Track lib changes ?
« Reply #16 on: September 10, 2010, 09:59:50 pm »
Is see.
Yet it is not an optimal solution. If I want my targets to be coherent, the "Windows" target of the GUI project should build both the OGRE and the SFML versions (as you pointed out). The thing is that the SFML version is absolutely not needed by the main project, but it will be listed as a required dependency, and as such, be compiled every time along with the OGRE version.

I agree my setup may be a bit weird, but my initial request would make things much simpler : I only need C::B to check if the library output file has changed, and if so, re-link.