| 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
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Tuesday, September 26, 2017 3:31 AM To: CDT General developers list. Subject: Re: [cdt-dev] Adding autotools support to core builder 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
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ang, Chin Huat
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 |