-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Trueman, Chris via Boost Sent: 19 February 2019 12:18 To: boost@lists.boost.org 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
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 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