Re: [cdt-dev] CDT 9.0 Build update

[Doug Schaefer <dschaefer@xxxxxxx>]

Sort of, yes. In fact, I¹d like to go as far as allow users to define
their own toolchains in the preference UI. Toolchain providers can still
use extensions to do that. And there should be API to let you do it
programmatically.

The new toolchain definitions at their root will be very minimal. That¹s
what I¹m trying to figure out, what that minimum is. So far, it¹s things
like error parsers, language settings providers, and a few other things.

Now if you want to use CDT¹s makefile generation or internal builder,
you¹ll need the old system and, yes, the managed build settings extension.
I can¹t see it being too difficult to graft that system onto the new one.
I think that will be more practical. Though if someone wants to work on
that, they can. This makefile generation helps with users transitioning
from Visual Studio who don¹t know how to write their own build files.

Doug


On 2015-07-29, 11:01 AM, "cdt-dev-bounces@xxxxxxxxxxx on behalf of Jesper
Eskilson" <cdt-dev-bounces@xxxxxxxxxxx on behalf of
jesper.eskilson@xxxxxxx> wrote:

>
>
>On 2015-07-29 16:30, Doug Schaefer wrote:
>> And, of course, feedback is appreciated. We need to make to this work
>> for everyone.
>
>How does this work affect toolchain integrators? Will it enable other
>ways to define toolchains other than the infamous XML-mess in plugin.xml?
>
>/Jesper
>
>> Doug.
>>
>> From: <cdt-dev-bounces@xxxxxxxxxxx <mailto:cdt-dev-bounces@xxxxxxxxxxx>>
>> on behalf of Doug Schaefer <dschaefer@xxxxxxx
>><mailto:dschaefer@xxxxxxx>>
>> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx
>> <mailto:cdt-dev@xxxxxxxxxxx>>
>> Date: Wednesday, July 29, 2015 at 10:20 AM
>> To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx
>> <mailto:cdt-dev@xxxxxxxxxxx>>
>> Subject: [cdt-dev] CDT 9.0 Build update
>>
>>     Hey gang, I spent the last day or so prototyping some ideas. My
>>     thinking as I mentioned in an other thread is to practice on the
>>     Arduino CDT plug-in and it¹s build and launch environment.
>>
>>     The experiment I¹m trying is how much can I do without the CDT
>>     managed builder plugins. The theory being, I should be able to build
>>     a new build system directly on the CDT core. It forces the new
>>     system to be minimal.
>>
>>     It also undoes a huge wrong that I and a few others feel happened
>>     when we introduced the managed build system changes back in 2006.
>>     We¹ve essentially forced all build systems to be built on the CDT
>>     managed build system. For simple cases where all you¹re doing is
>>     calling make, you really don¹t need all that complexity and it¹s
>>     pretty overwhelming to get things working.
>>
>>     Anyway, I¹m gathering notes on the wiki page as I go through the
>>     exercise. https://wiki.eclipse.org/CDT/Build/Doug. I¹ve also added
>>     some things that were missing from the Designs section, like how to
>>     hook up to launch configurations, an important consideration in the
>>     launch bar era.
>>
>>     Doug.
>>
>
>-- 
>Jesper Eskilson <jesper.eskilson@xxxxxxx>
>IAR Systems AB
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit
>https://dev.eclipse.org/mailman/listinfo/cdt-dev