Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] ScannerInfoProvider vs. PathEntryStore vs.CConfigurationDataProvider Extension Points

Hi Walter,

The New Project Model functionality will not break any public core
API/extensions available currently, so all existing custom build system
integrations should remain working. You can still use the
ScannerInfoProvider and other core API/extensions for integration with
the CDT core.


-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Brunauer, Walter
Sent: Friday, February 16, 2007 4:44 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] ScannerInfoProvider vs. PathEntryStore
vs.CConfigurationDataProvider Extension Points


I have a question regarding the different extension points/APIs
currently available to provide input to the CDT source code parser and
indexer services (or any other service using these APIs).

Some background first: I have my own build system, which is completely
independent of the CDT build system (different builder, own persistance
mechanism, etc.). For the managed build of this build system, I
currently use the ScannerInfoProvider extension point to provide include
paths and defines (which basically works).

Now I want to migrate towards the new CDT project model. I tried
PathEntryStore, but this seems to be rather complex. I also found
CConfigurationDataProvider, but that is probably more than I need.

What is the right entry point to use? What APIs do I really need to
implement, in case one of the two options I found is correct? Or can I
stay with ScannerInfoProvider also in the future?

Thanks a lot in advance,


Walter Brunauer
Senior Member Technical Staff
Workbench Group
Wind River Systems GmbH
Salzburg, Austria
+43 662 4579150 office
cdt-dev mailing list

Back to the top