Comments below. Good topics to argue over at EclipseCon
š.
- What about the build configuration stuff which is now tied to MBS?
Iām not sure what youāre asking.
At the end of the day, my objective is to be able to flush MBS and have an IDE that only has Core Build.
In general, Iāve been trying to tie UI associated with MBS with the MBS nature. Core Build projects do not have that nature so it should be hidden for them. If not, let me know and Iāll try and fix it.
- Can you elaborate on the effects of Core Build only working together with the launchbar? Surely you will be able to create launch configurations the old way? (I've heard several comments from people who don't
really like (or see the point of) the launchbar.)
The way Core Build works best is to use the properties from ILaunchTarget to select the appropriate IToolChain to be used for a build. The ILaunchMode selects whether to use a build config that is debug or release (run) or profile, etc. I am adding a Build
Settings tab to the Launch Descriptor Editor to edit build settings but that only appears if you launch it from the launch bar (it also shows the launch config tabs).
In general, Launch Configurations created the old way show up in the launch bar and if you provide the right providers, you can hook them up to Core Build.
I actually canāt image how Core Build will work without the Launch Bar and probably wonāt spend time on that. We at QNX are all in with the Launch Bar. Contributions accepted to do something else especially if it provides a good user experience.
BTW, both Xcode and Visual Studio have launch bars. The point is to simplify the launch experience. More on that at the summit too.
Just my thoughts, and I am open as always to be influenced to produce something better
š.
Doug.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Jesper Eskilson
Sent: Friday, September 29, 2017 2:13 AM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Adding autotools support to core builder
I've finally gotten around to some prototyping on core build together with our own build tools, and things are looking promising. (Our biggest problem at the moment is that our own build system needs an overhaul.)
Some questions:
- What about the build configuration stuff which is now tied to MBS?
- Can you elaborate on the effects of Core Build only working together with the launchbar? Surely you will be able to create launch configurations the old way? (I've heard several comments from people who don't
really like (or see the point of) the launchbar.)
--
/Jesper
Jesper Eskilson
Development Engineer
IAR Systems AB
Cool. Sounds like youāve made good progress.
I still think CMake is the best example to follow and look at everything Iāve done in the cmake.core and cmake.ui plug-ins. You do need your own new project wizard to set up the project nature
and generate initial files. I assume your toolchain is GCC so you donāt need a new one. But you will need a build configuration provider to map toolchains to build configurations. Again, you can look at the CMake build config provider to see how thatās done.
And feel free to ask detailed questions here or on Mattermost. I think there are a few people wondering how this all works.
And thatās where I will give a word of warning. I am in the middle of putting the final touches on a number of updates that will likely change how a few things work and will at least make things
more defined. Iāll be putting together a slide package for EclipseCon Europe with the results of my work here. We then have until the 9.4 release to test out the architecture on new things like the autotools work you are doing.
Also, Iām slowly coming around to the idea that CDTās core build will only work with the launch bar. Properties on the selected launch target selects the toolchain and each toolchain and launch
mode get a build configuration. Iām still trying to decide what to do with the default build configuration that projects get by default. That may end up being ārunā on the Local target, or it may end up being a null configuration and build configurations need
to be created and made active for them to work. Thatās an example of the type of things Iām working through right now.
And I havenāt even begun to understand how running the build tools in Docker or other remote machines, including Windows Subsystem for Linux from Windows Eclipse, needs to work in these scenarios.
That will come though.
Doug
Hi everyone,
Iām interested to make core builder support building both native and containerized versions of autotools project, my hope is to first enable native build and then use that as a
starting point to add container support. The containerized autotools project would be built and launched using Yocto Project toolchain containers, although other container images might also work.
Iād be happy to contribute both native and containerized versions of core builder autotools project, although given that Iām new here please bear with me as I try to familiarize
myself with the contribution process.
So far Iāve managed to prototype extending CBuildConfiguration to invoke autoreconf/configure/make directly, but thatās pretty much it for now. I could use some advice or guidance
on how to support new project type, project nature, build configuration, toolchain, etc. from core builder perspective. Any help that I can get to implement a more functional core builder autotools project would be much appreciated.
--Chin Huat