Re: [boost] 32/64 library name conflict under Windows?

Subject: Re: [boost] 32/64 library name conflict under Windows?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-03-12 17:21:11

AMDG

On 03/09/2016 04:59 AM, Peter Dimov wrote:
> Paul A. Bristow wrote:
> 
>> +1 for x86, x64, arm ...
> 
> +1.
> 
> Another thing that would be pretty nice for Windows/autolink users would
> be something like
> 
>    b2 --target libboost_date_time-vc80-mt-sgd-1_61.lib
> 
> to work, as the link error message one gets when the compiler/IDE can't
> find an autolinked library gives its name but it's not trivial to get
> from there to the required b2 command line.
> 

What does work now is:

b2 --build-type=complete msvc-8.0 libboost_date_time-vc80-mt-sgd-1_61.lib

This effectively says generate all the targets as
if you were building every possible combination,
and then actually build only files named libboost_xxx.

boost-git>b2 --build-type=complete libboost_system-vc140-mt-sgd-1_61.lib
-n -d1
<snip>
...found 1300 targets...
...updating 5 targets...
common.mkdir
bin.v2\libs\system\build\msvc-14.0\debug\link-static\runtime-link-static
common.mkdir
bin.v2\libs\system\build\msvc-14.0\debug\link-static\runtime-link-static\threading-multi
compile-c-c++
bin.v2\libs\system\build\msvc-14.0\debug\link-static\runtime-link-static\threading-multi\error_code.obj
msvc.archive
bin.v2\libs\system\build\msvc-14.0\debug\link-static\runtime-link-static\threading-multi\libboost_system-vc140-mt-sgd-1_61.lib
common.copy stage\lib\libboost_system-vc140-mt-sgd-1_61.lib
...updated 5 targets...

In Christ,
Steven Watanabe