Hi,
Sorry for the delayed response – was busy with some local
stuff here.
The "default" built-in include paths are calculated
using the
"org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile"
extension point.
A typical Scanner discovery profile usage is the following:
1.
A
tool-chain specific scanner discovery profile is defined by contributing to the
"org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile"
extension point.
2.
The
profile ID is associated with the tool-chain by specifying the profile id via
the inputType#scannerConfigDiscoveryProfileId or the
toolChain#scannerConfigDiscoveryProfileId attributes.
(see the build gnu tool-chain build fefinitions in the
org.eclipse.cdt.managedbuilder.gnu.ui plug-in for the reference implementation)
When the project is being created/loadded the profile
associated with the project/configuration tool-chain is queryied for the
default includes/symbols information.
So you will need to perform the two above steps in order to
provide the includes/symbols info specific for your tool-chain
If you do not want the builtin includes/symbols information
to be calculated at all you could simly associate no profile with your
tool-chain (i.e. ommit both of the above steps)
Regards,
Mikhail
No not yet i tried to replace existing include
paths in the configuration with my own using the template mechanism, my include
paths were added successfully but the defaults did not get replaced.
Regards,
Sheldon
On
7/31/07, Torkild Ulvøy Resheim
<turesheim@xxxxxxxxx>
wrote:
Hi
Sheldon,
On Friday 20 July 2007 10:16, Sheldon Dsouza wrote:
> 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
>
Did you find a solution to this? I'm looking into the same issue and cannot
find anything useful in documentation or source.
--
Torkild Ulvøy Resheim
Senior Design Engineer
Atmel Norway AS
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev