17 Mar
2017
17 Mar
'17
12:36 a.m.
On 17/03/2017 12:59, Tom Kent via Boost wrote:
Looks like neither is correct; should be "vc1410".
I submitted a pull request against develop to change to this, which matches the library output.
I asked this in another thread (I don't have a VS2017 install locally to check): what does $(PlatformToolsetVersion) in VS2017 C++ projects evaluate to? Because if that number is different than what Boost is putting in the filenames, it's going to cause integration pain to someone.