Re: [boost] Encoding address-model in library names

Subject: Re: [boost] Encoding address-model in library names
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2017-07-07 07:53:42

On 07/07/17 04:57, P F wrote:
> 
>> On Jul 6, 2017, at 2:52 AM, Andrey Semashev via Boost <boost_at_[hidden]> wrote:
>>
>> On 07/06/17 04:10, Gavin Lambert via Boost wrote:
>>> On 6/07/2017 10:00, Andrey Semashev wrote:
>>>> If we want to put binaries to the same directory, I think the name should include the architecture.
>>> At build time it's trivial enough to have your x86/64 libraries in one folder and your arm libraries in another; it might be convenient to have them in one place but I don't see this as compelling (but then I don't build arm binaries as a matter of course, so take that with a grain of salt).
>>
>> The described use case is to be able to build everything in one go, so that all binaries end up in the common stage directory.
> 
> If you set the same install prefix for each build tree then you can build and install everything in one go:
> 
> ls -1 | xargs -n1 -I {} cmake --build {} --config Release --target install
> 
> Or you can create a CPackConfig.cmake file, which build the installer for you from each variant all in one go as well:
> 
> include("64/CPackConfig.cmake")
> set(CPACK_INSTALL_CMAKE_PROJECTS
>      "32;Foo;ALL;/"
>      "64;Foo;ALL;/"
> )

I was talking about building Boost using Boost.Build.