That’s fine in some environments, but as soon more complex things like remote build servers, independent command-line building or just more control over the build process is needed, then the CDT managed build process is not really scalable. It makes porting harder to port from one target platform to another, because different vendors have different plugins, with incompatible settings. But this depends on the build plugins used. Key to this is CMake: I’m keeping the Eclipse CDT features, adding CMake with Make and Ninja to the fix, and have it ‘ruled’ by three different ’emperor’: Eclipse, Visual Studio Code and from a shell console: MCUXpresso SDK CDT project with CMake for Eclipse, Visual Studio Code and Command Line Building OutlineĮclipse CDT managed build projects greatly simplify project handling from a user perspective: create a project, add or remove source files and hit ‘build’, and everything is taken care of.
So what if I have an Eclipse project (say MCUXpresso IDE and SDK), and want to build it on a build server, and and I want to use the same time the project with Eclipse IDE and Visual Studio code?
In this article I want to rule a project with Eclipse CDT, Visual Studio Code and with building it from the command line for automated builds. A Triumvirate is or Triarchy is built by three individuals which lead or rule something.