CDT/Archive/planning/9.0/build

Requirements

Build without Eclipse

Everything needed to build a project has to be checked into source control. While Visual Studio and Xcode are ubiquitous on the platforms they support, Eclipse doesn't enjoy the same power position. To be good citizens in our community and with our users in particular, we shouldn't be forcing them to install Java and Eclipse and our plug-ins on build machines.

Now that doesn't mean we can't generate build files, but we have to do so in such a fashion that those build files are checked in and the tools can run against them without any extra tooling.

Other managed build systems as first class citizens

When CDT began and the managed build system was created, there weren't many popular managed build systems, e.g. systems that generate Makefiles, that we could rely on. Since then, tools such as autotools and CMake and a few others have become very popular. Qt also has it's own qmake to generate Makefiles.

We need to make it easy to plug in those systems into our build process. For example, we could add a step before running 'make' and provide a Java extension point to provide extensions that will do the right thing for those tools. We do have Builders right now but it's at the wrong place in the model.

Separate out managed build settings that feed into scanner discovery

Right now, you have to add managed build settings in order to integrate a toolchain using a regular Makefile build even though you're not using the managed build system. Right now the managed build model is the center of the universe. It needs to be separated out and optional so it's easier to add toolchains without going through the complex model.

User provided toolchains

It should be possible to add toolchains without writing an Eclipse plug-in. This could be done with something like a toolchain definition file with an editor that helps guide the user to add in their toolchain.