RE: [cdt-dev] Creating an input file based on project references

["Matthew Fortune" <Matthew.Fortune@xxxxxxxxxx>]

Hi,

I have been trawling through CDT and can't see an easy way of adding a
custom builder (or a nature that uses the builder) to a specific project
type. I am wanting to add another builder to run before either the
internal or managed make builder.

Can anyone point me in the right direction?

Regards,
Matthew

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On
> Behalf Of Matthew Fortune
> Sent: 24 June 2010 15:47
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Creating an input file based on project
references
> 
> > > I have got a new exported option type (currently called
executables)
> > which is successfully passing the executable file artifacts from one
> > project to the next (the plumbing to achieve that was relatively
> > significant). Now that I have the full set of executables in the
> 'final'
> > project my tool needs further information about the structure of the
> > workspace. Each executable may depend on one or more other
executables
> and
> > this is not encoded within the binaries.
> > >
> > > So in addition to being able to access the artifacts (which gives
me
> the
> > ability to re-build when they change), I need this extra
information.
> > >
> > > Does that make sense?
> >
> > You can get the references as part of the c project description
> manager
> > delta.
> > I've not tried to do anything similar to the above, so can't give
much
> > advice.  An alternative would be to run your final tool as a special
> > custom eclipse builder in the top-level project.  Having built the
> > references this could construct your tool command using whatever
> > custom logic you have.
> 
> Indeed. A custom builder was the best I could think up. I was debating
> how much effort that will turn out to be so thought it best to ask for
> suggestions.
> 
> I'll see what I can do in a builder.
> 
> Thanks for your suggestion.
> 
> Matthew
> 
> >
> > James
> > _______________________________________________
> > 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