Subject: Re: [boost] [release] 1.64.0 please test master snapshot..
From: Olaf van der Spek (ml_at_[hidden])
Date: 2017-03-18 06:49:41
On Sat, Mar 18, 2017 at 4:06 AM, Tom Kent via Boost
> My (semi-)personal dog in the fight:
> For the binary builds that we've put on sourceforge, the libraries are
> organized in directories based on the b2 command that was used to build
> them. This b2 toolset=msvc-14.0 address-model=32 would make
> boost_1_XX_0/lib32-msvc-14.0/. This could then be added to Visual Studio's
> link path (across multiple project files for different
> compilers/architectures) with boost_1_XX_0/lib$(
> PlatformArchitecture)-msvc-$(VisualStudioVersion)/. Then the libraries in
> that directory were named with libboost_thread_vc140-X-1_XX.lib, which
> matched the output from the config/auto_link.hpp pragma, so the library
> names were automatically included.
> Short of making our toolset= set to the visual studio version instead of
> any c++ toolset, this isn't going to work anymore. Thanks MS! :-(
With one VS version supporting multiple toolsets you can't use the VS
version anyway can you?
What is the problem when you use auto linking? The file names are a
detail and AFAIK all output files are staged into a single directory.