Subject: Re: [boost] Status of Visual Studio 2017 support
From: degski (degski_at_[hidden])
Date: 2017-02-20 23:32:33
On 20 February 2017 at 16:33, Tom Kent via Boost <boost_at_[hidden]>
> I strongly diagree with that. The primary use case for windows developers
> with visual studio is as a user of the headers and .lib/.dll files that
> come out of boost, inside their project files (configured with a gui to add
> include/library paths).
You seem to imply that the above is different for developers not on
windows (other than the "gui" being bash and vim).
Most users do not need boost build except for the
> step where they need to create the compatible static/dynamic libraries that
> they will later use.
Isn't the above what everybody does with any library (build and link in
> The issue here for most of them is that the current
> boost-build can't build libraries that are compatible with VS2017.
The libraries (any) built with VS2015 (VC14.0) will do equally well in this
(VC14.1) case, while at the same time VS2017 has not been released yet. The
current boost release pre-dates VS2017.
> The command line usage to build the boost libraries from the ground up
> needs to be dead-simple...
It IS dead simple, the boost build documentation could be pointier though.
> ...so that it can be followed even by developers who
> don't know what an environmental variable is.
Are they required to know how to turn on their computer, or is this also
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk