| Advice for large workspaces, multiple projects, third-party libs, executables, etc [message #210334] |
Mon, 25 February 2008 00:50  |
Eclipse User |
|
|
|
Hey all,
I had asked earlier about how to get the include paths from one project
incorporated into another within the same workspace. So, if I have
project B that uses project A, then can I update project A's include
paths without having to update project B's paths?
There doesn't seem to be a general solution to that, and I found that I
had to manually put all of the same include paths in myself. Someone
emailed me and suggested that I set up a reference to project A in B's
settings. I tried doing so, both in the
Properties -> Project References
and
Properties -> C/C++ General -> Paths and Symbols -> References tab
Neither one had the desired effect (i.e., adding a -I option to gcc's
command line for any of project A's includes). So, is there something
else that I should be setting? Similarly for third-party libraries that
I want to link in? This would be an insanely useful feature. It's not
one that MSVC includes either, so perhaps Eclipse is trying to follow
suit with them. If so, may I say: please DON'T! :) I do actually like
VC, but no need to repeat its mistakes :).
Similarly, what's the standard way of dealing with different executables
(i.e., different files that have a main() method)? Is my only option to
exclude those from the build of general projects, and then have a
separate project for each file with a main() function?
Anyway, if anyone can suggest a work-arounds or best practices, I'd love
to hear them.
Thanks.
Dave
|
|
|
|
Powered by
FUDForum. Page generated in 0.03248 seconds
Home