Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Scanner Discovery

Hi Sergey,
Thanks for the testing. I consider it important to maintain compatibility and it is encouraging sign. Also, even if the new scanner discovery is enabled, all old functionality is supposed to be accessible via MBS provider.


On Thu, Dec 22, 2011 at 8:34 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

On Thu, Dec 22, 2011 at 4:52 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:
I've tested compatibility of our in-house project configurator with sd_90 and didn't discover any issues.

I should have added that this applied to the mode where the new scanner discovery was disabled. Our code apparently has to change to provide includes and macros through the new API for it to work with the new scanner discovery enabled.


A minor cosmetic issue: the provider names displayed in the Providers tab should not contain "CDT" in their names since the convention is to never use "CDT" term in UI.


On Tue, Dec 20, 2011 at 8:43 PM, Andrew Gvozdev <> wrote:
I've been working on new design for scanner discovery, see and bug 290631. There are some scenarios how it could be used and screenshots at

At that point I've got working version on sd90 branch of CDT repository. The core machinery is done, and UI is usable.

Here are some highlights:
- scanner discovery is naturally associated with build configuration
- inspection of built-in compiler settings is done only once (per compiler), results are available to all projects in workspace
- algorithm of Build Output Parsers is more accurate, takes in consideration build folder, can recognize include and macro files (-include and -macros options), undefine (-U)
- handles EFS
- notification mechanism for changes in the language settings
- Mac Frameworks supported
- extension point for extenders, abstract classes for typical kinds of providers to extend
- means to plug discovery to resource listeners
- switch to back down to the legacy SD just in case

The code in cdt.core was tested, covered with JUnits and pretty well documented, although other parts (build plugins and especially UI) need clean-up/some more work.
The plan is to listen to community feedback and hopefully proceed with incorporating the core part to CDT master. I'd like to include it this early in the release cycle so to have room to fix issues should any arise. The rest is to be cleaned up and gradually added with the objective of Juno release.

So, I count on some feedback. The sd90 branch is being built on Hudson and can be downloaded at The code is, well, sd90 branch and API is concentrated in org.eclipse.cdt.core/model/org.eclipse.cdt.core.language.settings.providers package.


cdt-dev mailing list

cdt-dev mailing list

Back to the top