RE: [cdt-dev] Timing issues with build info?

[Doug Schaefer <DSchaefer@xxxxxxx>]

It's coming from the Preferences. The hardcoded default is the GCC one and
it gets added to your project whether you have gcc or not. This is way
wrong. It doesn't make sense to have a default. The toolchain needs to be
able to override this at any rate.

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: Tuesday, July 24, 2007 2:09 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Timing issues with build info?
> 
> Looking at my .cproject file, I see the GCCStandardMakePerProjectProfile
> there along with my clScannerInfo profile. And sometimes in the
> autodiscovery record, it shows the GCC one as selected! How did it get
> there
> to begin with? Back into the debugger...
> 
> 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: Tuesday, July 24, 2007 1:54 PM
> > To: CDT General developers list.
> > Subject: RE: [cdt-dev] Timing issues with build info?
> >
> > What I've done is simply created a complete new profile kinda like this:
> >
> > <extension
> >    id="clScannerInfo"
> >    name="Windows SDK Scanner Info Provider"
> >
> point="org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile">
> >       <scannerInfoCollector
> >
> class="net.sf.cdt_windows.msvc.build.WindowsScannerInfoCollector"
> >          scope="project">
> >       </scannerInfoCollector>
> > </extension>
> >
> > I then hooked it up to the inputType of my compiler.
> >
> > The info collector implements IScannerInfoCollector3 and, right now, all
> > it
> > does is return a IDiscoveredPathInfo that computes the include paths and
> > returns them in the getIncludePaths() method.
> >
> > It works most of the time but started seeing these timing issues when I
> > ran
> > the plugin in a runtime workbench (seems to work fine when exported and
> > run
> > normally). But I'm seeing the Default GCC collector instantiated every
> now
> > and then in my project's context. I don't know if we have the default
> > hardcoded to it somewhere, or whether we're picking one at random once
> in
> > a
> > while.
> >
> > BTW, with all this I may have no hair left soon either ;)
> >
> > 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 Chris Recoskie
> > > Sent: Tuesday, July 24, 2007 1:43 PM
> > > To: CDT General developers list.
> > > Subject: Re: [cdt-dev] Timing issues with build info?
> > >
> > > Personally if I had any hair left I'd be pulling it out right now.
> I've
> > > been trying to decipher the scanner info stuff so I can do a provider
> > for
> > > xlc, but it always seems to want to invoke an external scanner info
> > > generator, when like your QNX stuff, I don't have one.  Since I don't
> > have
> > > one, this causes NPEs in the MBS code :-(
> > >
> > > If anyone has suggestions as to how to get around this I would be very
> > > appreciative.
> > >
> > > I suspect once I get past that point, I will start running into the
> > > problem
> > > you mention...
> > >
> > > ===========================
> > >
> > > Chris Recoskie
> > > Team Lead, IBM CDT Team
> > > IBM Toronto
> > > http://www.eclipse.org/cdt
> > >
> > >
> > >
> > >
> > >              Doug Schaefer
> > >              <DSchaefer@xxxxxx
> > >              m>
> > To
> > >              Sent by:                  "CDT General developers list."
> > >              cdt-dev-bounces@e         <cdt-dev@xxxxxxxxxxx>
> > >              clipse.org
> > cc
> > >
> > >
> > Subject
> > >              24/07/2007 01:33          [cdt-dev] Timing issues with
> > build
> > >              PM                        info?
> > >
> > >
> > >              Please respond to
> > >                "CDT General
> > >              developers list."
> > >              <cdt-dev@eclipse.
> > >                    org>
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hey gang,
> > >
> > > I?ve been mucking around with my Windows SDK and my QNX toolchain
> > > integrations and scanner discovery and am seeing some weird behavior.
> I
> > am
> > > implementing my own scanner info collector since I can compute paths
> > > without having to run gcc like the default one does.
> > >
> > > The symptom is that my IScannerInfoCollector2 createPathInfoObject
> > method
> > > doesn?t get called at times and the DefaultGCC one does. And it
> appears
> > to
> > > be timing dependent since I put break points at different places and
> > > sometimes it does get called correctly.
> > >
> > > I doubt there are many people doing this, but has anyone else seen
> this.
> > > Are we still experiencing timing issues with the .cproject file
> > > reading/writing?
> > >
> > > 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
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev