|
Re: external scanner info generator warning [message #122246 is a reply to message #122111] |
Thu, 30 September 2004 14:30 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
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 #122302 is a reply to message #122268] |
Fri, 01 October 2004 15:19 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
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
|
|
|
|
Powered by
FUDForum. Page generated in 0.04026 seconds