Re: [cdt-dev] Include paths

["Mike Frysinger" <vapier.adi@xxxxxxxxx>]

On Thu, May 22, 2008 at 7:38 AM, Jesper Eskilson wrote:
> Wieant Nielander wrote:
>>> Now that the internal builder works (more or less) for my toolchain, I'm
>>> faced with the problem of telling the indexer how to figure out what include
>>> paths to use when looking for system include files. (I get warning-markers
>>> for example when including stdio.h, even though the file is compiled
>>> correctly.)
>>>
>>> There is an extension point called
>>>
>>> org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile
>>>
>>> but that seems only applicable to make-based builders. Another extension
>>> point is
>>>
>>> org.eclipse.cdt.managedbuilder.core.ScannerConfigurationDiscoveryProfile
>>>
>>> but I cannot find any documentation for it, and the plugin manifest
>>> editor won't let med create such an extension point.
>>>
>>> If anyone could point me in the right direction, I'd be grateful.
>>
>> It seems you do have to go with the
>>  org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile
>> extension point. Not sure about the managedbuilder.core version, but
>> both the std gnu toolchain and ours seem to work with the make.core
>> one. That extension allows you to specify a scanner info provider (in
>> general the compiler), a parser of the generated info and a collector
>> of the info (well, see the doc for that extension point).
>
> The org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile is
> unfortunately *very* sparsely documented, and doesn't help very much in
> understanding how the interface works. Some of it just doesn't parse as
> regular english:
>
> "Build output provider is make build or/and build output file."
>
> Anyway, I'll dig away and see what happens.

so if i create a new profile inside of
org.eclipse.cdt.managebuilder.core (copy and paste existing
GCCManagedMakePerProjectProfileC one for example), then simply update
the ID and Name, and obviously the specsFile -> run -> command field,
things work fine.  the item shows up in the drop down Discovery
Profile list in the Discovery Options tab and the include paths are
generated as expected for my gcc-based toolchain.

however, once this extension is relocated to my own plugin, it all
disappears from the expected locations.  moving it back and presto, it
shows up.

same goes for the extended information as exposed by
org.eclipse.cdt.make.ui.DiscoveryProfilePage in
org.eclipse.cdt.managebuilder.ui.  if i create a new profilePage in
that plugin, the extended info shows up.  move it to my plugin and it
all disappears.
-mike