No Defined Symbols? [message #173091] |
Mon, 17 July 2006 16:32  |
Eclipse User |
|
|
|
Hi,
My code uses defines like "_WIN32" and "linux". But CDT doesn't seem
to
have any predefined symbols like VC++, code::blocks, and Dev-Cpp. Why
doesn't CDT automatically detect its environment and define symbols? Does
the user have to define everything?
Thanks,
Nathan
|
|
|
|
|
|
Re: No Defined Symbols? [message #174099 is a reply to message #173168] |
Mon, 31 July 2006 08:01  |
Eclipse User |
|
|
|
Originally posted by: divis1969.mail.ru
Unfortunately, undefined symbols and unconfigured include directories
impacts the indexer and outline view.
This is the major disadvantage of the Eclipse CDT I see right know.
Sometimes, you need just to browse the bunch of code and the indexer is the
all that you need for this purpose. But if you don't have build output, if
this code have a lot of include directories and predefined symbols, you
cannot use CDT effectively.
So, when I create the new standard make project, I would prefer if CDT
indexer assumes each directory where .h files resides as an include
directory and each predefined symbol as already defined.
For example, the code base could have two different definitions of the same
function. Depending on #define statements you could work with one of them.
But I would like to see both of them under outline view.
I don't know, may be all of the above is already scheduled as future
enchancements of CDT?
Dmitry
"Norbert Ploett" <norbert.ploett@siemens.com> wrote in message
news:1153202292.790878@baruth.khe.siemens.de...
> Nathan,
>
> if you need predefined symbols you can set them in the project properties
> of managed make projects. Environment variables will generally passed
> through to the compiler although you can modify this thoo in the project
> properties.
>
> Eclipse does not of itself define any symbols.
>
> HTH
>
>
> Norbert
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03746 seconds