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.
-----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
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@lists.boost.org> 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@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 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
Thank you for taking the time to reply. Following your steps, b2 is still trying to use the VS2017 compiler that I have installed. I can't seem to make it choose the VS2019 compiler. Chris. -----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Mateusz Loskot via Boost Sent: 22 February 2019 11:35 To: boost@lists.boost.org Cc: Mateusz Loskot Subject: Re: [boost] Building Boost 1.69 with Visual Studio 1.69 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@lists.boost.org> 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@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 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 _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Sun, 24 Feb 2019 at 11:20, Trueman, Chris via Boost < boost@lists.boost.org> wrote:
Thank you for taking the time to reply. Following your steps, b2 is still trying to use the VS2017 compiler that I have installed. I can't seem to make it choose the VS2019 compiler.
Why is that relevant? Build with VS2017 and happily consume the libs with VS2019. degski -- *"Big boys don't cry" - **Eric Stewart, Graham Gouldman*
On Sun, 24 Feb 2019 at 10:20, Trueman, Chris <ctrueman@intellicorp.com> wrote:
Thank you for taking the time to reply. Following your steps, b2 is still trying to use the VS2017 compiler that I have installed. I can't seem to make it choose the VS2019 compiler.
I forgot completely about the project-config.jam modification. Here is more complete procedure 1. START > Visual Studio 2019 > x64 Native Tools Command Prompt 2. cd D:\boost.win 3. .\bootstrap.bat 4. Edit generated project-config.jam and replace using msvc ; with using msvc : 14.1 : "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Preview\\VC\\Tools\\MSVC\\14.20.27323\\bin\\HostX64\\x64\\cl.exe" ; 5. Before you fire b2, you can remove -nologo from this line in D:\boost.win\tools\build\src\tools\msvc.jam https://github.com/boostorg/build/blob/20d72776c8b61613f0e3b32d01b17f9ee013d... 6. Finally, run b2 .\b2 variant=debug address-model=64 --with-filesystem --with-test --layout=system ... compile-c-c++ bin.v2\libs\filesystem\build\msvc-14.1\debug\address-model-64\link-static\threading-multi\codecvt_error_category.obj Microsoft (R) C/C++ Optimizing Compiler Version 19.20.27323 for x64 Copyright (C) Microsoft Corporation. All rights reserved. cl "libs\filesystem\src\codecvt_error_category.cpp" -Fo"bin.v2\libs\filesystem\build\msvc-14.1\debug\address-model-64\link-static\threading-multi\codecvt_error_category.obj" -TP /Z7 /Od /Ob0 /W3 /GR /MDd /Zc:forScope /Zc:wchar_t /favor:blend /wd4675 /EHs -c -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 "-I." and you should see the CL 19.20.27323 from VS2019 is actually used, that is: D:\boost.win>cl /? | findstr optimized Microsoft (R) C/C++ Optimizing Compiler Version 19.20.27323 for x64 Copyright (C) Microsoft Corporation. All rights reserved. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Mateusz Loskot via Boost Sent: 24 February 2019 13:46 To: boost@lists.boost.org Cc: Mateusz Loskot Subject: Re: [boost] Building Boost 1.69 with Visual Studio 1.69
On Sun, 24 Feb 2019 at 10:20, Trueman, Chris <ctrueman@intellicorp.com> wrote:
Thank you for taking the time to reply. Following your steps, b2 is still trying to use the VS2017 compiler that I have
installed. I can't seem to make it choose the VS2019 compiler.
I forgot completely about the project-config.jam modification. Here is more complete procedure
1. START > Visual Studio 2019 > x64 Native Tools Command Prompt 2. cd D:\boost.win 3. .\bootstrap.bat 4. Edit generated project-config.jam and replace
using msvc ; with using msvc : 14.1 : "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Preview\\VC\\Tools\\MSVC\\14.20.27323\\bin\\HostX64\\x64\\cl.exe" ;
5. Before you fire b2, you can remove -nologo from this line in D:\boost.win\tools\build\src\tools\msvc.jam
https://github.com/boostorg/build/blob/20d72776c8b61613f0e3b32d01b17f9ee013d...
6. Finally, run b2
.\b2 variant=debug address-model=64 --with-filesystem --with-test --layout=system
... compile-c-c++ bin.v2\libs\filesystem\build\msvc-14.1\debug\address-model-64\link-static\threading- multi\codecvt_error_category.obj Microsoft (R) C/C++ Optimizing Compiler Version 19.20.27323 for x64 Copyright (C) Microsoft Corporation. All rights reserved.
cl "libs\filesystem\src\codecvt_error_category.cpp" -Fo"bin.v2\libs\filesystem\build\msvc-14.1\debug\address-model-64\link-static\threading-multi\codecvt_error_category.obj" -TP /Z7 /Od /Ob0 /W3 /GR /MDd /Zc:forScope /Zc:wchar_t /favor:blend /wd4675 /EHs -c -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 "-I."
and you should see the CL 19.20.27323 from VS2019 is actually used, that is:
D:\boost.win>cl /? | findstr optimized Microsoft (R) C/C++ Optimizing Compiler Version 19.20.27323 for x64 Copyright (C) Microsoft Corporation. All rights reserved.
This looks fine, except that what I really expect and want to be able to do is use BOTH 14.1 and 14.2 in one call of bjam/b2 b2 address-model=64 toolset=msvc-14.1,msvc-14.2 ... So I put this in my user-config.jam using msvc : # Version VS 2017 14.1 : # compiler location (Note that the file layout completely changed recently) "C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe" # 15.7.1 15May2018 for : # Options <define>BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE # Needed if you are working on develop or master ahead of the latest release. ; and the debug-config info said: # notice: will use 'C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe' for msvc, condition <toolset>msvc-14.1 # Used, for example, thus # b2 toolset=msvc-14.1 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. ; and the debug-config info said: # notice: will use 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Preview/VC/Tools/MSVC/14.20.27508/bin/Hostx64/x64/cl.exe' for msvc, condition <toolset>msvc-14.2 and I then used it like this for a hello_wordly example: b2 -a address-model=64 toolset=14.1 -d2 --debug-configuration > logfile.log The msvc.read-setup stage was this msvc.read-setup <p..\..\..\bin.v2\standalone\msvc\msvc-14.1\address-model-64\architecture-x86>msvc-setup.read file C:\Users\Paul\AppData\Local\Temp\jam2c1c11d5.000 REM "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\Build\vcvarsx86_amd64.bat" SET CommandPromptType=Cross SET DevEnvDir=C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\ SET ExtensionSdkDir=C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs SET Framework40Version=v4.0 and build and run was OK, but when I tried using 14.2 VS2019 preview b2 -a address-model=64 toolset=msvc-14.1 -d2 --debug-configuration >> logfile.log it failed here: ...skipped <p..\..\..\bin.v2\libs\hello_boost\example\hello_boost.test\msvc-14.2\debug\address-model-64\asynch-exceptions-on\link-static\runtim e-link-static\threading-multi>hello_boost.obj for lack of <p..\..\..\bin.v2\standalone\msvc\msvc-14.2>msvc-setup.nup... Of course what I really wanted to do was b2 -a address-model=64 toolset=msvc-14.1,msvc-14.2 > mylog.log but I thought I would check I could walk first ;-) Suggestions on where I am going wrong welcome. Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
AMDG 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.
<snip>
Suggestions on where I am going wrong welcome.
In Christ, Steven Watanabe
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe via Boost Sent: 25 March 2019 18:59 To: boost@lists.boost.org Cc: Steven Watanabe Subject: Re: [boost] Building Boost 1.69 with Visual Studio 1.69
AMDG
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. The log looked confused about both cl.exe and vsvarsall.bat. (I did a --clean and --reconfigure first to make sure) So, taking Steven's advice, I have now specified both compilers and both setups in my user-config.jam thus: using msvc : # Version VS 2017 14.1 : # Compiler location "C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe" : # Options <setup>"C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Auxiliary/Build/vcvarsall.bat" <define>BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE # Needed if you are working on develop or master ahead of the latest release. ; # Used, for example, thus # b2 toolset=msvc-14.1 using msvc : # Version VS 2019 Preview 14.2 : # Compiler location "C:/Program Files (x86)/Microsoft Visual Studio/2019/Preview/VC/Tools/MSVC/14.20.27508/bin/Hostx64/x64/cl.exe" : # Options <setup>"C:/Program Files (x86)/Microsoft Visual Studio/2019/Preview/VC/Auxiliary/Build/vcvarsall.bat" <define>BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE # Needed if you are working on develop or master ahead of the latest release. ; I:\boost\libs\hello_boost\example>b2 -a address-model=64 toolset=msvc-14.1,msvc-14.2 -d2 --debug-configuration > both_cl_setup.log runs with two promising messages: notice: will use 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe' for msvc, condition <toolset>msvc-14.1 notice: will use 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Preview/VC/Tools/MSVC/14.20.27508/bin/Hostx64/x64/cl.exe' for msvc, condition <toolset>msvc-14.2 and two runs of vcvarsall.bat as expected. An extract from the log (zip attached) from this command is not quite as I would expect with a confusing/confused warning. # notice: will use 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Preview/VC/Tools/MSVC/14.20.27508/bin/Hostx64/x64/cl.exe' for msvc, condition <toolset>msvc-14.2 # Used, for example, thus # b2 toolset=msvc-14.2 notice: Loading user-config configuration file 'user-config.jam' from 'C:/Users/Paul'. notice: [msvc-cfg] msvc-14.1 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe' warning: toolset msvc initialization: warning: can not find user-provided command 'C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe' warning: initialized from C:\Users\Paul\user-config.jam:101 warning: Did not find command for MSVC toolset. If you have Visual Studio 2017 installed you will need to specify the full path to the command, set VS150COMNTOOLS for your installation, or build from the 'Visual Studio Command Prompt for VS 2017'. notice: will use 'C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe' for msvc, condition <toolset>msvc-14.1 These two cl.exe listed above are the same file: 'C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe' 'C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe' but bjam uses the specified on just the same. Automatically finding msvc cl.exe and specifying it colliding? but both pass OK :-) Hello Boost! Platform: Win32 Compiler: Microsoft Visual C++ version 14.1 STL : Dinkumware standard library version 650 Boost : 1.70.0 _MSC_FULL_VER = 191627027 Hello Boost! Platform: Win32 Compiler: Microsoft Visual C++ version 1920 STL : Dinkumware standard library version 650 Boost : 1.70.0 _MSC_FULL_VER = 192027508 which looks plausible. _MSC_FULL_VER though it doesn't say 14.2 but 1920 instead. No doubt this will change when the 'official' release is out in several days' time. I'll try something more adventurous next ;-) Thanks Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
On Tue, 26 Mar 2019 at 15:13, Paul A. Bristow via Boost-build <boost-build@lists.boost.org> wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe via Boost Sent: 25 March 2019 18:59 To: boost@lists.boost.org 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 worked, obviously: I had been fiddling with that and possibly missed details about what actually worked.
<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! Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
On Mon, Mar 25, 2019 at 1:09 PM Paul A. Bristow via Boost < boost@lists.boost.org> wrote:
This looks fine, except that what I really expect and want to be able to do is use BOTH 14.1 and 14.2 in one call of bjam/b2
b2 address-model=64 toolset=msvc-14.1,msvc-14.2 ...
If that's not supported it would be a bug.
So I put this in my user-config.jam
using msvc : # Version VS 2017 14.1 : # compiler location (Note that the file layout completely changed recently) "C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe" # 15.7.1 15May2018 for
You shouldn't need to put in the cl.exe path. B2 is supposed to find it on its own. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
On Mon, 25 Mar 2019 at 20:00, Rene Rivera via Boost-build <boost-build@lists.boost.org> wrote:
On Mon, Mar 25, 2019 at 1:09 PM Paul A. Bristow via Boost <boost@lists.boost.org> wrote:
This looks fine, except that what I really expect and want to be able to do is use BOTH 14.1 and 14.2 in one call of bjam/b2
b2 address-model=64 toolset=msvc-14.1,msvc-14.2 ...
If that's not supported it would be a bug.
So I put this in my user-config.jam
using msvc : # Version VS 2017 14.1 : # compiler location (Note that the file layout completely changed recently) "C:/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.14.26428/bin/Hostx64/x64/cl.exe" # 15.7.1 15May2018 for
You shouldn't need to put in the cl.exe path. B2 is supposed to find it on its own.
Yes. Things seem to improved since my last e-mail where I described the hack. This should do the trick now, AFAICT: using msvc : 14.2 ; Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
participants (6)
-
degski -
Mateusz Loskot -
Paul A. Bristow -
Rene Rivera -
Steven Watanabe -
Trueman, Chris