RE: [cdt-dev] Scanner Info stuff

[Doug Schaefer <DSchaefer@xxxxxxx>]

Yup, that did it. Turns out to be pretty easy, once you know how :)

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 Doug Schaefer
> Sent: Sunday, May 20, 2007 1:16 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Scanner Info stuff
> 
> I think I found the secret. My scanner info collector has to implement
> IScannerInfoCollector3. I'll have to implement those methods and see if I
> can get it working.
> 
> 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 Doug Schaefer
> > Sent: Sunday, May 20, 2007 11:21 AM
> > To: CDT General developers list.
> > Subject: RE: [cdt-dev] Scanner Info stuff
> >
> > Well, that's not exactly what I was looking for. Right now with my gnu
> > toolchains, I specify a scannerConfigDiscoveryProfileId in the
> inputType.
> > I'm assuming it's the profile that creates the paths and symbols with
> the
> > built-ins for the compiler.
> >
> > I'm just trying to write my own profile but it's hard to make sense of
> the
> > extension point...
> >
> > 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 Sascha Radike
> > > Sent: Sunday, May 20, 2007 3:34 AM
> > > To: 'CDT General developers list.'
> > > Subject: Re: [cdt-dev] Scanner Info stuff
> > >
> > > Hi Doug,
> > >
> > > maybe this is what you are looking for ? It is really easy to
> implement.
> > > Only associating the provider with the configurations is a bit tricky.
> > >
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=181018
> > >
> > > Regards,
> > >
> > > Sascha
> > >
> > > ________________________________________
> > > Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> Im
> > > Auftrag von Doug Schaefer
> > > Gesendet: Samstag, 19. Mai 2007 17:24
> > > An: CDT General developers list.
> > > Betreff: [cdt-dev] Scanner Info stuff
> > >
> > > Hey gang, especially Mikhail S ☺.
> > >
> > > I’m trying out my Windows SDK integration and am finding that the
> > Includes
> > > container is messed. I had been relying on the envVarBuildPath to hook
> > up
> > > the INCLUDES environment variable to the include paths. That seems to
> be
> > > broken now (and I think I remember a bug flying by mentioning that).
> But
> > > I’d like to have a more general solution anyway.
> > >
> > > So how do I hook up my own code to the scanner info stuff. I don’t
> have
> > an
> > > external executable to run like the gcc provider stuff does. I just
> have
> > > some Java code that digs into the registry to find the locations of
> the
> > > Windows SDK install. And this is for internal build only as well. I
> > don’t
> > > need to scan build output (at least not yet). Sounds like it should be
> > > simple.
> > >
> > > Thanks,
> > > Doug Schaefer, QNX Software Systems
> > > Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> > >
> > >
> > > _______________________________________________
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev