Boost logo

Boost :

Subject: Re: [boost] CMake Announcement from Boost Steering Committee
From: Daniela Engert (dani_at_[hidden])
Date: 2017-07-19 12:47:52

Am 19.07.2017 um 14:30 schrieb Sergei Nikulov via Boost:
> 2017-07-19 15:19 GMT+03:00 Ion Gaztañaga via Boost <boost_at_[hidden]>:
>> CMake, for instance, does not really build. AFAIK, it generates build
>> instructions for the real build system.
That's my understanding, too.

>> This is unacceptable to me, I want something that really builds the program
>> and also runs tests from the command line
That are pretty much my requirements when switching through a ton of
different configurations of compiler versions / bitness (32 or 64) /
mode (debug or release) when I test changes to one of the 110 Boost
libraries, that I needed to fork.

> JFYI, same commands used on every system
> 1. generate> cmake ..
> 2. build> cmake --build .
> 3. test> ctest
Ok, so how do I fire off a libraries test-suite using f.i.
msvc-14.1/32/release concurrently to another one using f.i.
msvc-14.0/64/release (and may be some more)? I may be missing something.

At present I start one process using b2 with these three configuration
parameters for each one of the configuration tuples. Something similar
happens when I build a Boost distribution.


Boost list run by bdawes at, gregod at, cpdaniel at, john at