RE: [cdt-dev] Replacing the CDT's Make build system

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

When you say you already have a "CLI-based build system fully in place",
what does that exactly mean?  I'm assuming this means that not just the
code generation tools (i.e. compiler, assembler, linker) exist, but
rather that you have also a build system that wraps them (i.e. something
similar to make which is not itself based upon make).

If you have what I would call a "make-alike" CLI build system on top of
your tools, you could still use Managed Build as a basis for your
CDT-based build system, but you would write your own makefile generator,
dependency calculator, and toolchain definitions (which specify the
tools you are using and how they feed data from one tool to the next).
Creating all of these types of customized functionality is supported via
current extension points.  This would allow you to auto-generate
configuration files for your particular build tool, and invoke your tool
to do the build.

Does that fit your needs sufficiently?
___________________________________________
 
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 Hope Duryea
> Sent: Sunday, March 06, 2005 12:08 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: RE: [cdt-dev] Replacing the CDT's Make build system
> 
> Hi Chris,
> 
> Thanks for the reply. I had already read that article,
> but I'm still trying to fully absorb it. There were
> aspects of it that struck me as things I wouldn't need
> or in some cases even want (like auto-build) -- I
> guess it's just not clear to me why Eclipse is even
> dealing with the detail of my build at all, other than
> for the cancellation and problem-reporting... but I'm
> probably just still not quite understanding what it's
> really about.
> 
> The thing is, I already have a CLI-based build system
> fully in place and I've been asked to see about making
> it usable from within Eclipse. Much of the source
> (though not all of it) is C/C++, which is why I wanted
> to see about using the CDT for what it offers wrt
> handling C/C++ development. But also why I don't want
> any of the Make-based build stuff, not even as an
> option, since I'm not putting together a
> general-purpose development environment (if I were,
> they could just download the CDT :) What I -think- I
> should be able to do is just mostly UI stuff, to deal
> with specifying build configuration aspects (the build
> I deal with is all about configurability -- the actual
> building of the targets is the easy part :), then
> generate a command line and exec it, whenever they ask
> to build. Please correct me, though, if that thinking
> is way off. (I can try and spiffy things up later with
> wizards for adding new source subdirs and what-not,
> but for now, I just want to get the basics in place.)
> 
> I doubt if what I'll be doing would be generic enough
> to offer back, but maybe I could try to document what
> I had to do, in case anyone else ever wants to do the
> same.
> 
> 
> --- "Recoskie, Chris" <crecoskie@xxxxxx> wrote:
> > There are articles on eclipse.org that talk about
> > creating builders in
> > general.  The best place to start is reading those.
> >
> http://www.eclipse.org/articles/Article-Builders/builders.html
> >
> > Other than that, you need to know that the standard
> > that we have is that
> > any builders that CDT should care about have either
> > the cnature or
> > ccnature (depending on if the builder is C-based or
> > C++-based
> > respectively).  There is more that you will have to
> > do if you want all
> > the bits and pieces of CDT interacting properly with
> > your build system
> > (e.g. parsing your included files and such), but
> > that should be enough
> > to get you started I think if you follow the info in
> > the builder
> > articles and documentation.
> >
> > The topic of creating additional non-make based
> > builders for CDT came up
> > a couple of times this week at EclipseCon.  I'm sure
> > we'd all be
> > interested in hearing more about what you are doing.
> >  E.g., could you
> > tell us what your requirements are, and whether you
> > are you planning on
> > contributing such a build system to CDT?
> >
> > ___________________________________________
> >
> > 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 Hope Duryea
> > > Sent: Friday, March 04, 2005 7:19 PM
> > > To: cdt-dev@xxxxxxxxxxx
> > > Subject: [cdt-dev] Replacing the CDT's Make build
> > system
> > >
> > > Hi all,
> > >
> > > Being new to both Eclipse and the CDT, before I go
> > too
> > > far down the road I'm going, I thought I'd check
> > here
> > > and make sure it's the right way to go. I want to
> > > fully replace the Make-based build system of the
> > CDT
> > > (I don't want to add to or customize it, I don't
> > want
> > > anything Make-oriented in there at all). What I've
> > > done so far is to pick up all the CDT plugins,
> > except
> > > these:
> > >   org.eclipse.cdt.make.core_2.1.0
> > >   org.eclipse.cdt.make.ui_2.1.0
> > >   org.eclipse.cdt.managedbuilder.core_2.1.0
> > >   org.eclipse.cdt.managedbuilder.ui_2.1.0
> > >
> > > which I assume I can then replace with my own
> > stuff.
> > > So, questions... Is this the right approach? Has
> > > anyone done anything like this before? Is there
> > any
> > > documentation on adding a build system to the CDT,
> > or
> > > do I just have to read through the source for the
> > > Make-based stuff and get an idea of how it's done
> > from
> > > that (I'm guessing MakeCorePlugin.java is a good
> > place
> > > to start :)
> > >
> > > Thanks.
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam?  Yahoo! Mail has the best spam
> > protection around
> > > http://mail.yahoo.com
> > > _______________________________________________
> > > 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
> >
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev