$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [release] 1.64.0 Decision on VS2017 version number?
From: Peter Dimov (lists_at_[hidden])
Date: 2017-03-19 15:42:23
> https://github.com/boostorg/build/pull/183
This reminds me of a question I had:
# Known toolset versions, in order of preference.
.known-versions = 14.0 12.0 11.0 10.0 10.0express 9.0 9.0express 8.0
8.0express 7.1
7.1toolkit 7.0 6.0 14.1 ;
We put 14.1 last; is this what we want in the release, or was this a
temporary measure until the issues with 14.1 are sorted out, as they appear
now to have been?
Because traditionally, we place the newest version first; and on a VS 2017
installation with both 141 and 140 toolsets, the above will (as far as I can
see) pick and build with 14.0 if no toolset is given, which may be
surprising.