|Re: [cdt-dev] CDT 9.0 Build update|
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?
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
Back to the top