On 19/07/2017 14:57, Alain Miniussi via Boost wrote:
I have no problems to switch to CMake if:
- Cmake does everything Boost.Build does with the same or less work. I just enter 'make' in my build directories, cmake is re-called automatically if necessary. And it does a lot of thing I could not do with bjam (arbitrary feature detection mostly, seems a PITA with bjam). And I can switch between all my configurations just by changing the build directory which, when I need to test the cross product of various compilers/MPI, is a huge gain. I am not sure how to build an test N configuration at the same time with bjam without having N instance of the code tree. Maybe it's in the tutorial.
I test my libraries with the following lines in windows: MSVC b2 -j12 toolset=msvc-7.1,msvc-8.0,msvc-9.0,msvc-10.0,msvc-11.0,msvc-12.0,msvc-14.0,msvc-14.1 variant=debug,release address-model=32,64 debug-symbols=on MINGW b2 -j12 toolset=toolset=gcc-3.4c++03,gcc-4.1c++03,gcc-4.2c++03,gcc-4.3c++03,gcc-4.4c++03,gcc-4.5c++03,gcc-4.6c++03,gcc-5.3c++03,gcc-6.1c++03,gcc-6.2c++03,gcc-6.3c++03 variant=debug,release address-model=32 debug-symbols=on Not to mention link=static,shared runtime-link=static-shared, and all possible combinations. B2 compiles and executes it really fast. My question as a Boost developer is, can CMake do the same with similar performance (time/memory/disk,etc.)? Best, Ion