Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » CDT » Best practice for multiple-project executables
Best practice for multiple-project executables [message #794060] Wed, 08 February 2012 17:03 Go to previous message
Mauro Condarelli is currently offline Mauro Condarelli
Messages: 365
Registered: September 2009
Senior Member
Hi,
I'm a little lost on how to structure a moderately complex program.
I have (currently) just two executables which rely on several libraries.

In my workspace I have one project for each (static) library plus one for each executable artifact.

I correctly defined the dependencies via "Project References", but this doesn't seem to have any real effect.

I still had to:
- manually add include paths (-I...)
- manually add library names (-l...)
- manually add library paths (-L...)
- take care library paths for Debug configuration pointed to the Debug library subdir and Release configuration pointed to Release Subdir for libs.
- manually compile all projects because compiling an executable wouldn't pick up changes in a lib.

Is this correct?
Is there a "Better Way" to achieve a full compilation?
Would I be better off switching to a set of Makefile Projects (instesd of using "Generate Makefiles automatically"?

Can someone point me to the right documentation, please?

TiA
Mauro

Report message to a moderator

[Message index]
 
Read Message
Read Message
Previous Topic:Add an existing file to a project
Next Topic:Share sources between projects
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sat May 25 20:20:47 EDT 2013

Powered by FUDForum. Page generated in 0.05051 seconds