Boost logo

Boost :

Subject: Re: [boost] Building Boost 1.69 with Visual Studio 1.69
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2019-02-22 11:34:36


When building Boost with VS2019, for the time being,forget about the
toolset name.
Do not configure anything in user-config.jam or anywhere
Launch VS2019 command prompt, then ./bootstrap.bat and run b2
In --layout=verioned build, it will generate libraries named with 'msvc-14.1'.
Just accept that, ignoring the fact it mismatches the reality
or build with --layout=system.

I have managed to run MP11 and System tests
https://gist.github.com/mloskot/4d34a6f6d0e60a543f2ed153af87dcd9
https://gist.github.com/mloskot/efbfb2b33c99b8f70cfe4f912a8ec4d6

I use VS2019 for Boost.GIL development, building required Boost libraries with
b2 --with-filesystem --with-test --layout=system
This way, GIL's CMakeLists.txt can detect the Boost libraries fine
and I can build and run GIL tests i VS 2019.

ML

On Fri, 22 Feb 2019 at 12:25, Paul A. Bristow via Boost
<boost_at_[hidden]> wrote:
>
> If you are confused about what is going on using b2 (sadly, a not unusual state :-( for one daft language writing another daft
> language), I find
>
> b2 --debug-configuration and -d2 ... produces much output, but also potential illumination.
>
> Windows path are a minefield and there is a special place in hell for whoever allowed spaces in failenames, and muddled back and
> forward slashes.
>
> \ is the escape char, so if you really want a \, convert to \\. Typically needed for Windows filenames.
>
> If you really want a ", put \" ...
>
> HTH
>
> Paul
>
>
>
>
> > -----Original Message-----
> > From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Trueman, Chris via Boost
> > Sent: 19 February 2019 12:18
> > To: boost_at_[hidden]
> > Cc: Trueman, Chris
> > Subject: [boost] Building Boost 1.69 with Visual Studio 1.69
> >
> > Maybe I'm getting ahead of myself given the recent topic about picking a version number for the latest MSVC toolset but I'm
> > having trouble building boost 1.69 with Visual Studio 2019 preview. I blindly assumed the toolset was 14.20 (given the directory
> > where cl.exe is found). Letting b2 determine the version yields vc141 in the lib names. Trying to force 142 with:
> >
> > using msvc : 14.2 : <path to cl.exe> ;
> >
> > in project-config.jam yields errors about unescaped characters.
> >
> > Suggestions welcomed.
> >
> >
> >
> > Chris.
> >
> > INTELLICORP LEGAL NOTICE: This E-Mail message and all attachments transmitted with it are intended solely for the use of the
> > addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended
> > recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that
> > any dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you received
> this
> > message in error, please notify the sender immediately by replying to this message, and then delete it.
> >
> > _______________________________________________
> > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

-- 
Mateusz Loskot, http://mateusz.loskot.net

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk