Re: [cdt-dev] CDT 10.0?

[Jesper Eskilson <Jesper.Eskilson@xxxxxxx>]

I think I will be able to push a gerrit commit soon to at least allow users to select a build configuration for Core Build projects. For a start, it will only allow users to select a build configuration, but not add/remove configurations.

/Jesper

Jesper Eskilson Development Engineer
IAR Systems AB

---

From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Friday, November 3, 2017 12:47 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] CDT 10.0?

 

Thanks Jasper!

I think Renesas will also be interested in bringing a managed build UI to Core Build. And QNX will be working on Standard Build. And Intel with Autotools and Docker which should lead to general remote builds.

It's all coming together. Thank you all!

Sent from my BlackBerry - the most secure mobile device - via the Rogers Network

From: Jesper.Eskilson@xxxxxxx

Sent: November 3, 2017 2:46 AM

To: cdt-dev@xxxxxxxxxxx

Reply-to: cdt-dev@xxxxxxxxxxx

Subject: Re: [cdt-dev] CDT 10.0?

Btw, I've just opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=526789 on the issue of making the build configuration UI available to Core Build projects.​

/Jesper

Jesper Eskilson Development Engineer
IAR Systems AB

---

From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Thursday, November 2, 2017 7:15 PM
To: CDT General developers list.
Subject: [cdt-dev] CDT 10.0?

 

Hey gang,

 

This just crossed my mind and you’re the first to hear about it ��. I’d like to do a bunch of clean up for Photon where Core Build becomes the main build system. As a result I’d like to clean up a bunch of the UI. A few things have crossed my mind.

• Remove the new C Project and C++ Project in favour of the new new C/C++ Project wizard that uses the new template engine. The old wizards are still accessible from there but would be hidden otherwise.
• Decide between the Global build console and the per Project build console. I favour the Global one but we should start that discussion. There really shouldn’t be two.
• Is there anything we can do so there’s only one Memory view?

 

And I’d take the opportunity of the major version bump to clean up the mess I’ve made of the Core Build interfaces and parent classes as we solidify the final API.

 

Happy to hear concerns about that, it is a crazy thought. Or if you like it.

Thanks,

Doug.