Eclipse Community Forums: C / C++ IDE (CDT) » external scanner info generator warning

Home » Language IDEs » C / C++ IDE (CDT) » external scanner info generator warning

external scanner info generator warning [message #122111]

Wed, 29 September 2004 07:29

Eclipse User

hi!

The first time I create a project for my toolchain [selected in Build
Target of Managed Make], I get the following warning:

"Error launching external scanner info generator (gcc -E -P -v
D:/eclipse_platform/eclipse/workspace/.metadata/.plugins/org .eclipse.cdt.make.core/specs.c) "

Does this mean that by default it searches for the GNU path rather than
the path of the toolchain selected?

What is the solution to suppress this warning?

thanks and regards,
Monali

Re: external scanner info generator warning [message #122246 is a reply to message #122111]

Thu, 30 September 2004 10:30

Eclipse User

Originally posted by: vhirsl.ca.ibm.com

When a managed project is created, as a part of project initialization,
ManagedMake will run a part of ScannerConfigurationDiscovery feature that
tries to read compiler's internal include paths and symbol definitions
from the gcc 'specs' file.
You can change the default command from Preferences->C/C++->New Make
Projects->Discovery Options. There you can specify a command appropriate
for your toolchain, or if there is not such a command, you can disable
'generate scanner info command'.
Note: this will affect all new make projects both standard and managed.

Thanks,
Vmir

Re: external scanner info generator warning [message #122268 is a reply to message #122246]

Fri, 01 October 2004 05:02

Eclipse User

Hi Vmir!

I already follow what you have written but I want the paths discovered for
my toolchain instead of 'gcc'. I have written a managed build plug-in for
my toolchain and I would like the scanner Info generator to search for its
specs file rather than the gcc specs file. Can this be done in the plug-in
instead of manually doing the changes in Preferences?

I did find that the function getESIProviderCommand()has 'gcc' hard-coded
in it.
Is this accessible so that I can pass my compiler to it?

thanks and regards,
Monali

vhirsl@ca.ibm.com wrote:

> When a managed project is created, as a part of project initialization,
> ManagedMake will run a part of ScannerConfigurationDiscovery feature that
> tries to read compiler's internal include paths and symbol definitions
> from the gcc 'specs' file.
> You can change the default command from Preferences->C/C++->New Make
> Projects->Discovery Options. There you can specify a command appropriate
> for your toolchain, or if there is not such a command, you can disable
> 'generate scanner info command'.
> Note: this will affect all new make projects both standard and managed.

> Thanks,
> Vmir

Re: external scanner info generator warning [message #122302 is a reply to message #122268]

Fri, 01 October 2004 11:19

Eclipse User

Originally posted by: vhirsl.ca.ibm.com

Hi Monali,
There are several ways to do it:
1. You can change org.eclipse.cdt.make.core project's manifest
(plugin.xml). There is an ExternalScannerInfoProvider extension point
there and 'defaultCommand' and 'defaultAttributes' parameters define the
command.

2. You can follow the example of ManagedBuild's function
calculateEntriesDynamically, where you can change values retrieved from
preferences before invoking the provider.

3. You can provide your own extension of ExternalScannerInfoProvider
extension point.

For quickest results I would recommend option 2.

Good luck,
Vmir

>Hi Vmir!
>
>I already follow what you have written but I want the paths discovered
for
>my toolchain instead of 'gcc'. I have written a managed build plug-in for
>my toolchain and I would like the scanner Info generator to search for
its
>specs file rather than the gcc specs file. Can this be done in the
plug-in
>instead of manually doing the changes in Preferences?

>I did find that the function getESIProviderCommand()has 'gcc' hard-coded
>in it.
>Is this accessible so that I can pass my compiler to it?
>
>thanks and regards,
>Monali

Re: external scanner info generator warning [message #122386 is a reply to message #122302]

Mon, 04 October 2004 08:50

Eclipse User

hi Vmir!

Thanks a lot for the quick help - I have opted for option 1 currently
and would work on option 3 later.

best regards,
Monali

vhirsl@ca.ibm.com wrote:

> Hi Monali,
> There are several ways to do it:
> 1. You can change org.eclipse.cdt.make.core project's manifest
> (plugin.xml). There is an ExternalScannerInfoProvider extension point
> there and 'defaultCommand' and 'defaultAttributes' parameters define the
> command.

> 2. You can follow the example of ManagedBuild's function
> calculateEntriesDynamically, where you can change values retrieved from
> preferences before invoking the provider.

> 3. You can provide your own extension of ExternalScannerInfoProvider
> extension point.

> For quickest results I would recommend option 2.

> Good luck,
> Vmir

> >Hi Vmir!
> >
> >I already follow what you have written but I want the paths discovered
> for
> >my toolchain instead of 'gcc'. I have written a managed build plug-in for
> >my toolchain and I would like the scanner Info generator to search for
> its
> >specs file rather than the gcc specs file. Can this be done in the
> plug-in
> >instead of manually doing the changes in Preferences?

> >I did find that the function getESIProviderCommand()has 'gcc' hard-coded
> >in it.
> >Is this accessible so that I can pass my compiler to it?
> >
> >thanks and regards,
> >Monali

Previous Topic:	CDT + 3.1?
Next Topic:	how to do nightly build from Eclipse

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Nov 06 22:11:23 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter