Re: [boost] [Boost-testing] Running regression tests for msvc-14.2 (preview)
On Tue, Feb 26, 2019 at 7:13 AM Mateusz Loskot via Boost-Testing < boost-testing@lists.boost.org> wrote:
On Tue, 26 Feb 2019 at 14:02, Tom Kent via Boost-Testing
wrote: I was hoping to start running regression tests for the upcoming Visual Studio 2019 (toolset 14.2) and got stumped by an issue. I've set a user-config.jam: using msvc : 14.2 ;
Is this toolset even supported?
As I explained in https://lists.boost.org/Archives/boost/2019/02/245143.php, I had to 'fake' it as 14.1 in project-config.jam:
using msvc : 14.1 : "C:\\Program Files (x86)\\Microsoft Visual
Studio\\2019\\Preview\\VC\\Tools\\MSVC\\14.20.27323\\bin\\HostX64\\x64\\cl.exe"
I was able to get the regression tests to run using this workaround in user-config.jam. Here's what the config_info is: https://www.boost.org/development/tests/develop/developer/output/teeks99-tes... I'm disappointed that we can't have general support for future versions of msvc. We don't seem to have this problem with pre-release versions of GCC/Clang. https://www.boost.org/development/tests/develop/developer/output/teeks99-02-... Tom
On Thu, Feb 28, 2019 at 6:34 AM Tom Kent
On Tue, Feb 26, 2019 at 7:13 AM Mateusz Loskot via Boost-Testing < boost-testing@lists.boost.org> wrote:
On Tue, 26 Feb 2019 at 14:02, Tom Kent via Boost-Testing
wrote: I was hoping to start running regression tests for the upcoming Visual Studio 2019 (toolset 14.2) and got stumped by an issue. I've set a user-config.jam: using msvc : 14.2 ;
Is this toolset even supported?
As I explained in https://lists.boost.org/Archives/boost/2019/02/245143.php, I had to 'fake' it as 14.1 in project-config.jam:
using msvc : 14.1 : "C:\\Program Files (x86)\\Microsoft Visual
Studio\\2019\\Preview\\VC\\Tools\\MSVC\\14.20.27323\\bin\\HostX64\\x64\\cl.exe"
I was able to get the regression tests to run using this workaround in user-config.jam.
Here's what the config_info is:
https://www.boost.org/development/tests/develop/developer/output/teeks99-tes...
I'm disappointed that we can't have general support for future versions of msvc. We don't seem to have this problem with pre-release versions of GCC/Clang.
https://www.boost.org/development/tests/develop/developer/output/teeks99-02-...
I've also gotten a run through with the new "rc" that came out today: https://www.boost.org/development/tests/develop/developer/output/teeks99-msv...
Success!!!
After this was merged:
https://github.com/boostorg/build/pull/401
I'm getting successful builds on develop :-)
C:\Python27-32\python.exe run.py --runner=teeks99-msvc142rc
--toolset=msvc-14.2 --bjam-options="-j4 address-model=64" --tag=develop
user-config.jam
using msvc : 14.2 ;
using python
: 2.7 # version
: C:\\Python27-32\\python.exe # Interperter/path to dir
: C:\\Python27-32\\include # includes
: C:\\Python27-32\\libs # libs
: <address-model>32 <address-model> # conditions
;
using python
: 2.7 # version
: C:\\Python27-64\\python.exe # Interperter/path to dir
: C:\\Python27-64\\include # includes
: C:\\Python27-64\\libs # libs
: <address-model>64 # conditions
;
https://www.boost.org/development/tests/develop/developer/output/teeks99-msv...
Now we need to get the tests to all cycle, then merge to master? Can this
make 1.70?
On Thu, Feb 28, 2019 at 8:39 PM Tom Kent
On Thu, Feb 28, 2019 at 6:34 AM Tom Kent
wrote: On Tue, Feb 26, 2019 at 7:13 AM Mateusz Loskot via Boost-Testing < boost-testing@lists.boost.org> wrote:
On Tue, 26 Feb 2019 at 14:02, Tom Kent via Boost-Testing
wrote: I was hoping to start running regression tests for the upcoming Visual Studio 2019 (toolset 14.2) and got stumped by an issue. I've set a user-config.jam: using msvc : 14.2 ;
Is this toolset even supported?
As I explained in https://lists.boost.org/Archives/boost/2019/02/245143.php, I had to 'fake' it as 14.1 in project-config.jam:
using msvc : 14.1 : "C:\\Program Files (x86)\\Microsoft Visual
Studio\\2019\\Preview\\VC\\Tools\\MSVC\\14.20.27323\\bin\\HostX64\\x64\\cl.exe"
I was able to get the regression tests to run using this workaround in user-config.jam.
Here's what the config_info is:
https://www.boost.org/development/tests/develop/developer/output/teeks99-tes...
I'm disappointed that we can't have general support for future versions of msvc. We don't seem to have this problem with pre-release versions of GCC/Clang.
https://www.boost.org/development/tests/develop/developer/output/teeks99-02-...
I've also gotten a run through with the new "rc" that came out today:
https://www.boost.org/development/tests/develop/developer/output/teeks99-msv...
On Sat, 2 Mar 2019 at 14:33, Tom Kent via Boost
Success!!!
Thumbs up! Now we need to get the tests to all cycle, then merge to master? Can this
make 1.70?
Please, with release of 14.2 being close, not having this would break vcpkg build, i.e. we'd have to wait for 1.71. degski -- *"Big boys don't cry" - **Eric Stewart, Graham Gouldman*
On Sat, Mar 2, 2019 at 6:33 AM Tom Kent via Boost-Testing < boost-testing@lists.boost.org> wrote:
Now we need to get the tests to all cycle, then merge to master? Can this make 1.70?
There's plenty of time for build changes to make it to 1.70. It might not make the beta rc though. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
On Thu, Feb 28, 2019 at 6:34 AM Tom Kent via Boost-Testing < boost-testing@lists.boost.org> wrote:
I'm disappointed that we can't have general support for future versions of msvc. We don't seem to have this problem with pre-release versions of GCC/Clang.
As far as B2 is concerned it would be as easy as using the compiler reported version for the B2 toolset version. But that would probably mean breaking everyones build files. Which I'm fine with, but I can see others might not be. In all of this it doesn't help that msvc versions are so horribly muddled. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
participants (3)
-
degski
-
Rene Rivera
-
Tom Kent