On Thu, Mar 16, 2017 at 7:47 PM, Tom Kent via Boost
On Thu, Mar 16, 2017 at 7:36 PM, Gavin Lambert via Boost < boost@lists.boost.org> wrote:
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.
$(PlatformToolsetVersion) is "141".
Personally I would prefer 14.10 (aka 1410) because of purely selfish reasons. As it would mean Boost Predef already says that "14.10" is the version. But otherwise I don't care what version number it is. I'm beyond exhausted from dealing with VS version numbers. Which means.. 1. For the beta the version is "14.10", aka "1410". 2. And we'll apply the Boost Config patch accordingly. 3. After beta everyone can fight over what the "real" version number should be. 4. Apply changes after enough people agree. And if that's fast enough.. We can do another beta. Other we just wait for the release to have the change. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail