On Sat, Mar 18, 2017 at 7:41 AM, Peter Dimov via Boost < boost@lists.boost.org> wrote:
Olaf van der Spek wrote:
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 >
On Sat, Mar 18, 2017 at 4:06 AM, Tom Kent via Boost < boost@lists.boost.org> wrote: 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$(PlatformArch itecture)-msvc-$(VisualStudioVersion)/.
...
With one VS version supporting multiple toolsets you can't use the VS
version anyway can you?
That's a good point. If I use, say, VS 2015 with the v120 toolset, I need to link to the vc120 libraries, not to the vc140 ones. So it seems that boost_1_XX_0/lib$(PlatformArchitecture)-vc$(PlatformToolsetVersion)/ is better.
I agree that this matches better with the way MS has evolved the platform, so does that mean that we should change boost build to match e.g. b2 toolset=vc-141? If so, should we retroactively add support (along side existing syntax) to allow b2 toolset=vc-140, b2 toolset=vc-80? Tom