RE: [cdt-dev] adding tools to *existing* toolchains?

["Andras Varga" <andras@xxxxxxxxxxx>]

Hi Wieant,

It was exactly my intention: to add yacc (and other tools) support to CDT.
Technically it is of course feasible to add that feature as an unrelated
plugin (there are some difficulties such as guaranteeing the order of
builders in .project, but these can be solved).

However, CDT already has beautiful tool support, with declarative Options,
OptionCategories, Input and Output types and all, and all necessary UI
elements (Tool Settings project property page, etc), so it would be just
great if we could use that. I'd just contribute the Yacc tool to the base of
the toolchain hierarchy.

If that was possible, I bet we'd see dozens of plug-ins like "Bison/Flex
integration for CDT", "SWIG integration for CDT" etc pop up on sites like
eclipse-plugins.info.

Is there some serious technical restriction in the CDT design that makes
this impossible?

Regards,
Andras

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Wieant Nielander
> Sent: Wednesday, December 12, 2007 1:57 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] adding tools to *existing* toolchains?
> 
> 
> > Why can't I contribute tools, macro resolvers etc to EXISTING
> toolchains?
> > Would be much better than "subclassing" each and every existing
> toolchain!
> >
> > In the Eclipse platform, I don't have to subclass from Perspective, View
> etc
> > definitions in plugin.xml to be able to contribute things (actions etc)
> to
> > them!
> >
> > See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=212127
> 
> Perhaps you can take another approach to this matter. When you want to
> add tools generating C code you can do that outside of CDT, i.e. you
> can write a plugin that uses its own nature, builder, property pages
> etc. E.g. when you want to add yacc support, you can add a builder
> that reacts on resources with .y extension and generates .c and .h
> files from it. Once these resources are added to the project, CDT should
> automagically take the appropriate actions to deal with them.
> 
> Regards,
>   Wieant
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev