Subject: Re: [boost] [release] 1.64.0 please test master snapshot..
From: Beman Dawes (bdawes_at_[hidden])
Date: 2017-03-16 21:53:46
On Thu, Mar 16, 2017 at 5:03 PM, Rene Rivera via Boost <
> On Thu, Mar 16, 2017 at 4:00 PM, Tom Kent via Boost <boost_at_[hidden]
> > On Thu, Mar 16, 2017 at 7:09 AM, Rene Rivera via Boost <
> > boost_at_[hidden]> wrote:
> > > After help from various sources to get the VS2017 building working the
> > > latest master snapshot should at least try and build with VS2017.
> > Assuming
> > > nothing horrible shows up today we will release the first beta tonight.
> > > Hence, please smoke test the latest master snapshot found at:
> > >
> > > <https://dl.bintray.com/boostorg/master/>
> > >
> > VS2017 is not yet working with master. When building the libraries it
> > builds in the format "libboost_thread-vc1410-mt-1_64.lib", however the
> > code
> > in config/auto_link.hpp still has a vc150 in it, meaning any time you try
> > to link a library you will get an error "libboost_thread-vc150-mt-1_
> > not found".
> > I think that is easy enough to fix (and drastic enough) that we should
> > the beta for it, but I defer to the release team.
> Does master config have the changes for this? Does develop config? What are
> the changes?
After a pull on both,
# define BOOST_LIB_TOOLSET "vc141"
but C:\boost\master\libs\config\include\boost\config\auto_link.hpp lines
# define BOOST_LIB_TOOLSET "vc150"
IIUC, develop is correct, while master is out-of-date.
So it looks like at the least develop for config needs to be merged into
master for config.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk