[SOLVED] pathes in a useful way [message #726403] |
Sat, 17 September 2011 18:26  |
Eclipse User |
|
|
|
Hey, I've been developing c++ for years with a default text editor and makefiles & commandline commands.
Lateley I took some break to switch to java and I got used to eclipse.
So now I don't want to return to my old editor and installed CDT.
I can write projects, I can even compile them.
Anyways I have a big problem. The only way I see to add include paths and librarys is each by hand. Given a very little framework, there will be around 100 actions I have to do.
I see 2 solutions for that:
1. Let CDT use pkg-config to define the includes and libraries.
2. Add includepaths and libraries recursively (and don't tell me I should #include <whatever/framework.h>).
Now both solutions aren't perfect, and I didn't managed to even get one to work. So for the moment I'm back to console compileation.
Hopefully someone knows a way out of this (since I don't beliefe that all of you include 5000 files by hand if you include e.g. qt)
[Updated on: Sun, 18 September 2011 17:18] by Moderator
|
|
|
|
|
Re: pathes in a useful way [message #726588 is a reply to message #726574] |
Sun, 18 September 2011 17:17  |
Eclipse User |
|
|
|
alright, I found a tricky way to do it now.
With the use of the tool mentioned in my last post, I added the pkgconfig includes to Gnu C Compiler includes and the libraries to Gnu C++ Linker.
God know's why it doesn't add the includes to Gnu C++ Compiler, anyways, I've done this by manually editing the .cproject file (done a fake Gnu C++ Compiler include to find where I should insert the includes).
With the Includes in both Compilers it is working.
I've created a Bug report for the plugin, hopefully they'll add the C++ part.
Anyways, I'd say "solved"
|
|
|
Powered by
FUDForum. Page generated in 0.07333 seconds