[cdt-dev] Re: Scanner Configuration Discovery for Standard Make

["Delicia" <deliciap@xxxxxxxxxx>]

Never mind, I figured it out - needed to update my UI plugin using the "org.eclipse.cdt.make.ui.DiscoveryProfilePage" extension point.

Now, I have 4 items in the "Discovery List":

- GCC Scanner Info per project profile

- GCC Scanner Info per file profile

- MY Scanner Info per project profile

- MY Scanner Info per file profile

 

"GCC Scanner Info per project profile" appears as the default.

Is it possible to change the default to "MY Scanner Info per project profile"?

 

Another question:

Is it important to extend the "org.eclipse.cdt.core.ScannerInfoProvider" point defining element 'cextension (run)'?

I couldn't figure out the significance of the above.

 

Any help would be appreciated.

Thanks,

Delicia.

 

---

Date: Wed, 18 Oct 2006 12:41:48 +0530
From: "Delicia" <deliciap@xxxxxxxxxx>
Subject: [cdt-dev] Scanner Configuration Discovery for Standard Make
To: <cdt-dev@xxxxxxxxxxx>
Message-ID: <040b01c6f284$c7343490$4301a8c0@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi,

    I have used the 'org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile' extension point to customize the scanner
for 'myGcc'.
This works nicely in a 'Managed Make Project'

However, for Standard Make, the "Discovery Options" tab shows CDT's defaults, i.e.
Discovery profile: GCC per project/file scanner info profile
Compiler invocation command: gcc

How can I get my customized scanner config changes to reflect in a 'Standard Make' project as well?
I read on one of the newsgroup discussions, that the scanner discovery profile has an advantage of being CDT-wide (as opposed to MBS options).

The wizard for a new Standard Make project uses CDT's class [class="org.eclipse.cdt.make.ui.wizards.NewMakeCProjectWizard"].

Thanks,
Delicia.
P.S. I'm now using CDT 3.1.x