| Some Eclipse / CDT questions [message #735839] |
Wed, 12 October 2011 16:45  |
Eclipse User |
|
|
|
Apologies if any of these questions have previously been posted. I did search for them, both on these forums and in the Eclipse help files, but didn't find any answers.
I've gained enough familiarity with Eclipse (after having first installed it almost 2 weeks ago) to build C++ applications and use the majority of Eclipse features, but a few questions remain unanswered.
My questions are:
1. What is the 'Compiler Version' drop-down list used for under Project Properties | C/C++ Build | XL C/C++ Compiler?
2. What is the purpose of 'Build Variables' under Project Properties | C/C++ Build, and how does it differ from 'Environment'? (I ended up using the latter to create differences between my Debug and Release configurations, e.g. using library files with debug info for the former but not for the latter. I couldn't get 'Build Variables' to do anything, though).
3. What is the best way to export Libraries and Library Paths from Project Properties | C/C++ General | Paths & Symbols? The export option only seems to be available for Includes and Symbols.
4. How can I specify the content of the default Makefile generated in a new C/C++ Makefile project (i.e. by selecting File | New | C/C++ Project | Makefile Project)? I have some Makefile customisations I would prefer to use for every new project.
Regards & thanks,
--- Victor.
|
|
|
|
|
| Re: Some Eclipse / CDT questions [message #736852 is a reply to message #736668] |
Fri, 14 October 2011 07:49  |
| Eclipse User |
|
|
|
Axel Mueller wrote on Fri, 14 October 2011 18:53Quote:2. What is the purpose of 'Build Variables' under Project Properties | C/C++ Build, and how does it differ from 'Environment'? (I ended up using the latter to create differences between my Debug and Release configurations, e.g. using library files with debug info for the former but not for the latter. I couldn't get 'Build Variables' to do anything, though).
'Build Variables' are Eclipse internal variables that you can use e.g for your custom build command. Environment variables are passed to the external shell that executes the build command. So is there some reason that this doesn't occur for the default 'make' command used with MinGW? Or is that not run in a command shell that inherits these build variables?
Axel Mueller wrote on Fri, 14 October 2011 18:53Quote:3. What is the best way to export Libraries and Library Paths from Project Properties | C/C++ General | Paths & Symbols? The export option only seems to be available for Includes and Symbols.
What do you want to achieve?
Never mind. I just reread the Help files again, and realised what the relation is between project references and marking paths & symbols as exported.  I didn't quite get that before, but it makes sense now. I marked my desired library modules and library paths to be exported in a given project configuration, then in another project selected that configuration as an external reference, and saw how the library modules and library paths automatically got added to the 2nd project.
Thanks for the tips, Axel.  I can see you've done this before, too; your marks are all over these forums!
|
|
|
Powered by
FUDForum. Page generated in 0.24979 seconds
Home
. I've thoroughly searched the Eclipse help files, the CDT FAQ, and these forums, before posting these questions.