Directory Management [message #903500] |
Fri, 24 August 2012 00:16 |
Taylor Snead Messages: 1 Registered: August 2012 |
Junior Member |
|
|
In the past few days, in search of an IDE with better code completion in Linux than Code::Blocks (With my project, the parser would crash into a memory leak that'd take 2gb of ram), I came upon Eclipse CDT (I hadn't really thought of Eclipse as a C++ IDE before) and really like it so far. My only problem is the limited and complicated management of the different directories, like source, build, and output. In something like Visual Studio, these are easily configurable with Build Dir, include dirs, and output dir options. But, with Eclipse, it seems that a project always MUST reference files in relation to ProjectFolder/Configuration (in my case, "Code/Linux"). I understand this more when using Make, to store all the makefiles in a separate dir, but even so I'd put the source and makefiles in the same dir for that. I'm using the internal builder instead of Make, and in building, it creates the Code/Linux dir and source files are referenced in relation to that. I can live with this, but it gets annoying when looking through settings seeing inconsistencies because the front-end for adding include dirs shows them relative to the project directory.
As a topic more related to GCC/G++ but still belonging in this thread about directory configuration, how can the linker be told through Eclipse to find the object files in a certain other directory (eg. a specified build directory)?
I'm thinking it shouldn't be too difficult to simply use a few user project environment variables for output dir and build dir (For putting the object files and retrieving them for linking), I just am not sure how (with my unfamiliarity with Eclipse).
[Updated on: Fri, 24 August 2012 00:19] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.03627 seconds