How to integrate PreMake / CMake into a C ++ build workflow

I am looking at PreMake / CMake at the moment. However, I do not see how this can be used in the entire cross-platform build stream. Indeed, it generates make files (or solutions). Then, how do you actually create these solutions on each target platform? Do I need to maintain one script construct for each target (e.g. .sh or .bat file)? This could defeat the purpose of using a tool such as premake / CMake in the first place.

A link to a tutorial showing the whole process from coding to the final built product using premake will be great.

Thanks for any help.

+4
source share
1 answer

Our main development is also done in C ++. We use CMake + ANT. VisualStudio for Windows, Xcode for Mac and iOS. Some build tools are written in Python.

It works pretty smoothly. We have single and low-level component tests that run directly from the assembly (using the CMake CTest mechanism, which we slightly manipulated - CMake - Open Source). Higher-level component and system tests are performed using a custom structure written in C # (we had a lot of debate about whether to use something ready-made or to write ourselves, in the end we decided that any ready-made structure should be modified so much that it was worth writing from scratch myself, I still wonder if this was the right decision).

We bind things together with ANT - mainly using <exec> calls at the lowest level, but also using well-installed extensions (such as ftp and svn). Our CI runs on Jenkins, which connects to the lower layers of the assembly through ANT.

+5
source

All Articles