That's tremendously helpful - many thanks.
Best wishes.
Tim Burgess
-----Original Message-----
From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of
Steven Watanabe via Boost-users
Sent: 28 February 2018 15:53
To: Tim Burgess via Boost-users
I downloaded the modular Boost master from Git Hub, as per instructions and built it on Windows as follows:
.\Bootstrap .\b2 headers .\b2
This generated (amongst others) the following libs for boost::filesystem:
libboost_filesystem-vc141-mt-gd-x32-1_67.lib libboost_filesystem-vc141-mt-gd-x64-1_67.lib libboost_filesystem-vc141-mt-x32-1_67.lib libboost_filesystem-vc141-mt-x64-1_67.lib
I then tried to build a static release X64 version of my application using VS2017 and got:
1>LINK : fatal error LNK1104: cannot open file 'libboost_filesystem-vc141-mt-s-x64-1_67.lib'
Obviously, I don't have this file, though I had thought that .\b2 was supposed to build all targets. So, I tried:
--build-type=complete will build all variants. The default is to build only the most common.
.\b2 link=static
This still does not generate the required file - where am I going wrong, please?
It's runtime-link=static (link=static controls whether Boost is built as a static library or a dll.). To build a specific library by name, you can use: b2 --build-type=complete libboost_filesystem-vc141-mt-s-x64-1_67.lib
BTW, I have checked that my project's library path points to the appropriate boost\stage\lib folder.
In Christ, Steven Watanabe _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users