RE: [cdt-dev] Extract tool chain definition?

["Recoskie, Chris" <crecoskie@xxxxxx>]

I don't mind making the changes (won't be until early next week at
best... I'm tied up for the rest of the week), but it means that Leo
will have to reorganize the work that he's doing to put his updated
toolchains into the new plugin.

Leo, are you ok with that?

___________________________________________
 
Chris Recoskie
Software Designer
IDE Frameworks Group
Texas Instruments, Toronto
 
 

> -----Original Message-----
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Thomas Fletcher
> Sent: Wednesday, October 13, 2004 9:08 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: RE: [cdt-dev] Extract tool chain definition?
> 
> +1 ... if you submit the code changes =;-)
> 
> It sets a good precedent for future changes coming down the line with
> respect to supporting various toolchains.  Even though there may be a
> default implementation that is provided with CDT, we should always
allow
> the OEM'able versions to ship with just base set of plugins that
provide
> a framework only functionality ... like the debugger.
> 
> Thomas
> 
> > -----Original Message-----
> > From: cdt-dev-admin@xxxxxxxxxxx
> > [mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf Of Recoskie, Chris
> > Sent: October 11, 2004 8:41 PM
> > To: cdt-dev@xxxxxxxxxxx
> > Subject: RE: [cdt-dev] Extract tool chain definition?
> >
> > I brought this up with respect to our requirements for 3.0
> > but I see no reason that we couldn't do this any sooner (say
> > for 2.1).  Any objections?
> >
> > How does org.eclipse.cdt.managedbuilder.toolchain.gnu sound?
> >
> > ___________________________________________
> >
> > Chris Recoskie
> > Software Designer
> > IDE Frameworks Group
> > Texas Instruments, Toronto
> >
> >
> >
> > > -----Original Message-----
> > > From: cdt-dev-admin@xxxxxxxxxxx
> > [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> > > Behalf Of Alex Chapiro
> > > Sent: Sunday, October 10, 2004 7:38 PM
> > > To: cdt-dev@xxxxxxxxxxx
> > > Subject: [cdt-dev] Extract tool chain definition?
> > >
> > > Is it possible to extract
> > > org.eclipse.cdt.managedbuilder.core.ManagedBuildInfo
> > extension point
> > > definition to a separate fragment to let easy get rid of
> > unnecessary
> > > build targets I think it is a vendor-specific issue, isn't it? Or
> > there
> > > is other way to control the list of available targets? Right now
we
> > are
> > > not support cygwin, but "GNU on Windows" is still available in the
> > list
> > > of configurations when I create new managed make builder project.
> > Would
> > > its description be placed  to a separate fragment, I could
> > not include
> > > this fragment in the release set of plugins.
> > > _______________________________________________
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx
> > > http://dev.eclipse.org/mailman/listinfo/cdt-dev
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev