[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Re: Setting project description confusion

For me the real problem is dealing with all the id's that are used to hook things together. If we used real Java inheritance and getters/setters and JDT's content assist, it would be a lot easier. The other thing I've run into is the need for dynamic toolchain definitions. There are some mechanisms in the XML to add in hooks but being all in Java would allow you do much more.

On Wed, Sep 30, 2009 at 2:00 AM, kesselhaus <kesselhaus@xxxxxxx> wrote:
Hmm, and I thought by the time the XML format was introduced (was that in CDT 2.x or 3.x?), that it would make an toolchain setup much easier by just adapting the XML file, rather than hardcoding the build chain in a Java-only plugin.


Am 18/09/2009 13:50, schrieb Doug Schaefer:
Interesting discussion... :). I'm definitely on the side doing a more flexible/dynamic tool chain integration mechanism that allows for the complete definition in Java. As always, contributions welcome ;).

:D.

On Fri, Sep 18, 2009 at 5:16 AM, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:
On 18 Sep 2009, at 09:37, Jesper Eskilson <jesper.eskilson@xxxxxx> wrote:

"ability" implies that it is a good thing to be able to do it.

I have the ability to run Windows on my computer; doesn't mean that it's a good thing (or even, that I'm likely to do it).

Alex

_______________________________________________
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