Boost logo

Boost :

Subject: Re: [boost] Encoding address-model in library names
From: Olaf van der Spek (ml_at_[hidden])
Date: 2017-07-08 07:49:26

On Fri, Jul 7, 2017 at 7:49 PM, P F <pfultz2_at_[hidden]> wrote:
>> On Jul 7, 2017, at 3:26 AM, Olaf van der Spek <ml_at_[hidden]> wrote:
>> On Fri, Jul 7, 2017 at 3:46 AM, P F via Boost <boost_at_[hidden]> wrote:
>>> You should just need to define CMAKE_PREFIX_PATH as that is the variable you use in cmake to tell it where dependencies are(even on windows). Using BOOST_ROOT is more for refining how boost is found when multiple version exists in the CMAKE_PREFIX_PATH. So if you install all your dependencies(ie boost, openssl, zlib, etc) in some directory say C:\deps32 and C:\deps64 then all you need to do is set the CMAKE_PREFIX_PATH for each version:
>>> alias cmake32=‘cmake -G \'Visual Studio 14 2015\' -DCMAKE_PREFIX_PATH=C:\deps32 -DCMAKE_INSTALL_PREFIX=C:\deps32’
>>> alias cmake64=‘cmake -G \'Visual Studio 14 2015 Win64\' -DCMAKE_PREFIX_PATH=C:\deps64 -DCMAKE_INSTALL_PREFIX=C:\deps64’
>>> Then cmake32/cmake64 sets up cmake with the different address models, and there is no need to worry about setting custom variables such as BOOST_ROOT. You just create separate build trees for each variant instead.
>> I'd like to build all variants in one go.. having to cd to each build
>> tree manually is cumbersome.
> There is no need to cd into each build directory. The `--build` flag takes the build directory, and like I showed in another email, you can build everything all in one go with:
> ls -1 | xargs -n1 -I {} cmake --build {} --config Release

On Windows?

This assumes the build dirs have been created and populated already doesn't it?
It still seems quite cumbersome.

> Or you could do:
> alias b='ls -1 | xargs -n1 -I {} cmake --build {} --config Release’
> So all you have to type is `b` and it builds everything in one go.


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