Subject: Re: [boost] [Boost-build] Building Boost 1.69 with Visual Studio 1.69
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2019-03-26 16:10:38
On Tue, 26 Mar 2019 at 15:13, Paul A. Bristow via Boost-build
> > -----Original Message-----
> > From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Steven Watanabe via Boost
> > Sent: 25 March 2019 18:59
> > To: boost_at_[hidden]
> > Cc: Steven Watanabe
> > Subject: Re: [boost] Building Boost 1.69 with Visual Studio 1.69
> > On 3/25/19 12:09 PM, Paul A. Bristow via Boost wrote:
> > >
> > > <snip>
> > > using msvc
> > > : # Version VS 2019 preview
> > > 14.2
> > > : # compiler location (Note that the file layout completely changed recently)
> > > "C:/Program Files (x86)/Microsoft Visual Studio/2019/Preview/VC/Tools/MSVC/14.20.27508/bin/Hostx64/x64/cl.exe"
> > > : # Options
> > > <define>BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE # Needed if you are working on develop or master ahead of
> > the latest release.
> > > ;
> > I recommend adding <setup>"C:/path/to/vcvarsall.bat"
> > I don't know whether this will fix everything, but
> > the immediate cause of the errors that you're seeing
> > is that the location of vcvarsall.bat is version dependent
> > and Boost.Build fails to find it.
> Correct, as ever.
> Sadly, hoping it would 'Just work', as others suggested with user-config.jam
> using msvc : 14.1 ;
> using msvc : 14.2 ;
> didn't work for me.
Possibly, I run b2 from "x64 Native Tools Command Prompt for VS 2019 Preview",
that is why that short definition for 14.2 in project-config.jam
I had been fiddling with that and possibly missed details about what
> <setup>"C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Auxiliary/Build/vcvarsall.bat"
I have just learned about the <setup> trick. This looks very useful!
-- Mateusz Loskot, http://mateusz.loskot.net