Hi Sheldon,
If your tool name is gcc
and it is the first on the PATH setting for your project/configuration, then your
gcc should be queried for paths (as you expect)
Does it work for you?
Mikhail
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sheldon Dsouza
Sent: Friday, July 20, 2007 12:17
PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Change in
default include paths
Ho Doug,
as you mentioned the includes are obtained from gcc itself, we are using
a different toolchain so where can i make the change for the scanner discovery
feature to ask my version of gcc for the includes.
Regards,
Sheldon
On 7/9/07, Doug
Schaefer <DSchaefer@xxxxxxx>
wrote:
These paths are coming from gcc itself. The
scanner discovery feature asks it for it's built-ins and that's what we're
getting.
If you have paths that aren't gcc defaults that
you'd like to add, I'd recommend creating a project template that would add in
those paths for you. Documentation for that is in the ISV docs and you can look
at our built-in HelloWorld templates as examples.
Hi,
When a C project
is created in CDT, the following default system include paths /usr/local, /usr/local/include etc are
added to the project properties. I need to modify these include paths for my
project creation, how do i go about this and which are the source files that i
have to change.
Regards,
Sheldon
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev