RE: [cdt-dev] RE: Includes Discovery Compiler

[Doug Schaefer <DSchaefer@xxxxxxx>]

Cool. Thanks. I guess the case I was thinking about was with standard make
where the scanner discovery parses the build output and sets various build
options for use by CDT's parsers. I think that is much harder.

Doug Schaefer
QNX Software Systems
Eclipse CDT Project Lead
http://cdtdoug.blogspot.com
 

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Alex Yin
Sent: Thursday, August 03, 2006 12:15 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] RE: Includes Discovery Compiler

Hi Norbert and Doug,

Thanks for the quick responses, they are very helpful. After trying the 
suggestions, it is working pretty well. Here is what I did:

1. Look at the plugin "org.eclipse.cdt.managedbuilder.core", it extends 
"org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile".

2. Create a similar extension in one of the plugins created for our toolset,

and make sure the "command" in "scannerInfoProvider->Run" is the right 
compiler.

3. In the plugin which extends the managed make build definitions, search 
for scannerConfigDiscoveryProfileId, and replace the value 
"org.eclipse.cdt.managedbuilder.core.GCCManagedMakePerProjectProfile" with 
the profile created in step 2.

No single line of code is needed.

Thanks,
--alex

>Date: Thu, 3 Aug 2006 15:34:10 +0200
>From: "Ploett, Norbert" <norbert.ploett@xxxxxxxxxxx>
>Subject: AW: [cdt-dev] Includes Discovery Compiler
>To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>Message-ID:
>
<88AEA5AC18A141439A0D954EB037B0D306CBC358@xxxxxxxxxxxxxxxxxxxxxxxxxx>
>Content-Type: text/plain;	charset="iso-8859-1"
>
>Hi Alex,
>
>you need to provide a different scanner configuration discovery profile. 
>The extension point is
>
>org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile
>
>and if you create a new extension you can click on "Open extension point 
>description" in the manifest editor to view the documentation.
>
>It's been a few weeks since I used this point to make the managed build 
>system use my gcc cross compiler on Cygwin so and I'll have to dig in my 
>memory if you have more questions about the details.
>
>HTH
>
>
>Norbert Ploett
>
>
>-----Ursprüngliche Nachricht-----
>Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im 
>Auftrag von Alex Yin
>Gesendet: Donnerstag, 3. August 2006 02:49
>An: cdt-dev@xxxxxxxxxxx
>Betreff: [cdt-dev] Includes Discovery Compiler
>
>Hi,
>
>In CDT, there is a feature to automatically discover the standard include
>paths. By default, the compiler in use is "gcc" for both standard and
>managed make.
>
>We have a toolset for C programming, which is different from GNU. To enable
>the managed make for this toolset, a few plugins created (mostly the UI
>portion). The question is: how to change the default compiler for include
>path discovery?
>
>In the standard make C project, there is a tab "Discovery Options", which
>accepts a different command other than "gcc". But there is no such thing 
>for
>managed make C project.
>
>I remember seeing some messages talking about enabling a different toolset
>in CDT, but not sure if the includes discovery mechanism was discussed or
>not.
>
>The Eclipse version is 3.1.0 and the CDT version is 3.0.0.
>
>Thanks,
>--alex
>

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev