[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Scanner info macro file
|
I simply used the dedicated extension point
org.eclipse.cdt.core.ScannerInfoProvider. Well, this is what is said
next to its definition:
<!--
========================================================================
=========== -->
<!-- Obsolete extension point, use the IPathEntry mechanism to provide
include/macros -->
<!--
========================================================================
=========== -->
So I also provided my own implementation of the extension point
org.eclipse.cdt.core.PathEntryContainerInitializer (which basically is
only a wrapper of my ScannerInfoProvider, except the implementation of
IPathEntryContainerExtension.isEmpty()).
Its getting complicated...
Walter
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Wieant Nielander
> Sent: Dienstag, 04. Dezember 2007 11:45
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Scanner info macro file
>
> > Well, seems IScannerInfoCollector is indeed missing this
> API. Anyway,
> > there is a very clear connection from IScannerInfoProvider to
> > IExtendedScannerInfo. So far for the API itself. My own
> > ScannerInfoProvider using my own ExtendedScannerInfo is completely
> > independent of CDT and works just fine, also with include and macro
> > files. I can't comment on CDT internal implementation
> details, but I
> > doubt the IExtendedScannerInfo is not considered somehow by the
> > AST/PDOM, so you are probably just looking at the wrong
> place. But if
> > CDT indeed does not use this information, it probably
> should be fixed
> > then...
>
> Well poking around PDOM is what lead me to
> IExtendedScannerInfo, so that seems to be ok. I'm currently
> just missing the link between it and my scanner info
> provider, so I'm interested in how you linked your own
> ScannerInfoProvider. My situation is that I'm having a
> managed build project with a toolchain defining a
> ScannerConfigurationDiscoveryProfile that allows me to define
> an IExternalScannerInfoProvider, not an IScannerInfoProvider?
>
> Thanks,
> Wieant
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
