On 7/12/19 7:15 PM, Michael Caisse via Boost wrote:
On 7/12/19 01:59, Andrey Semashev via Boost wrote:
May I merge Boost.WinAPI to master?
https://github.com/boostorg/winapi/commit/bb91190323166485a338b416446020a47b...
Fixes compilation of Boost.Thread (and dependent libraries) with MSVC-12 on x86.
https://github.com/boostorg/winapi/commit/f2789c82a4b16c9f6645fb10c0db6c62be...
A test for the above.
https://github.com/boostorg/winapi/commit/65b9c99a6772add56a24272d0b76b611fd...
Fixes compilation of BOOST_INTERLOCKED_* macros on Cygwin64.
Have the windows test runners cycled with this change?
Most of them did, including MSVC-12. We don't have official Cygwin runners. Appveyor CI for Boost.WinAPI has jobs for all MSVC and Cygwin and it passed all jobs: https://ci.appveyor.com/project/Lastique/winapi/builds/25875547
What is the breadth/variation of compilers/Windows OS versions that we have seen this cycle for?
Our official testers are limited to various MSVC versions: https://www.boost.org/development/tests/develop/developer/winapi.html Appveyor CI jobs are run on: - 32-bit x86: - MSVC-9, 10, 11, 12, 14.0, 14.1 - Cygwin - MinGW, MinGW-w64 (gcc 6.3.0) - 64-bit x86: - MSVC-12, 14.0, 14.1 - Cygwin64 - MinGW-w64 (gcc 7.3.0) I also ran the interlocked tests on MSVC-7.1 and 8 locally.