The Carbide.c++ team at Nokia has just published a series of articles that explains the Carbide.c++ build system in-depth and how to get the most out of it. A recommended read for all developing software with Carbide.c++.
- Building a better build system-Part 1: Introduces improvements done in Carbide.c++ 1.3 for detecting MMP file changes and dependency tracking using the compiler
- Building a better build system – Part 2 Concurrent builds: Explains using parallel compilation using Carbide.c++
- Building a better build system – Part 3 Eclipse incremental builder: Explains the benefit of using the Eclipse incremental builder. Note that there’s a small issue/bug with the incremental builder if you are using multiple SDKs, it won’t automatically detect that you’ve switched SDKs and hence fail to build the new target, even if its not built. Only applicable where you have a project that’s been created/imported to use more than a single SDK
- Building a better build system – Part 4 Benchmarking: Puts everything into perspectiva and summerizes by listing the pros/cons of using different build options and how that results into build speed