MSVC 2019 and 1.70 beta
Hi, Is 2019 not properly supported yet?
Building Boost.Build engine 'cl' is not recognized as an internal or external command, operable program or batch file.
Failed to build Boost.Build engine. Please consult bootstrap.log for further diagnostics.
From a dev prompt it doesn't appear to work either:
********************************************************************** ** Visual Studio 2019 Developer Command Prompt v16.0.0-pre.4.2 ** Copyright (c) 2019 Microsoft Corporation ********************************************************************** C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview>cd /vc C:\vc>cd boost_1_70_0 C:\vc\boost_1_70_0>bootstrap.bat Building Boost.Build engine Generating Boost.Build configuration in project-config.jam for msvc... Bootstrapping is done. To build, run: .\b2 To generate header files, run: .\b2 headers To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: .\b2 --help - Getting started guide: http://boost.org/more/getting_started/windows.html - Boost.Build documentation: http://www.boost.org/build/ C:\vc\boost_1_70_0>b2 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'. Performing configuration checks - default address-model : none - default architecture : none Building the Boost C++ Libraries. error: No best alternative for libs/context/build/asm_sources next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched -- Olaf
On Thu, Mar 14, 2019 at 4:48 AM degski via Boost <boost@lists.boost.org> wrote:
On Thu, 14 Mar 2019 at 10:25, Olaf van der Spek via Boost < boost@lists.boost.org> wrote:
Is 2019 not properly supported yet?
It's not released yet [i.e. it's a moving target], so seems normal to me.
Build support for VS 2019 RC (msvc-14.2) is on develop in boost build. Do we want to merge that to master for the release? I'm pretty confident that it isn't a "moving target" anymore, any VC features are surely locked down by now. However, adding that could raise issues downstream. Are there libraries that would also need to update? Does anyone see issues in the teeks99-07-v16d column on the develop regression tests? https://www.boost.org/development/tests/develop/developer/summary.html
Tom Kent wrote:
Build support for VS 2019 RC (msvc-14.2) is on develop in boost build. Do we want to merge that to master for the release?
Taking all release dates into account, I think that the right thing to do would be to release Beta 2 with 2019 support, so that people can give it a go. There's still time before the 1.70 release for another beta, but this creates extra work for the release manager, so it would be his call.
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Peter Dimov via Boost Sent: 14 March 2019 14:25 To: boost@lists.boost.org Cc: Peter Dimov Subject: Re: [boost] MSVC 2019 and 1.70 beta
Tom Kent wrote:
Build support for VS 2019 RC (msvc-14.2) is on develop in boost build. Do we want to merge that to master for the release?
Taking all release dates into account, I think that the right thing to do would be to release Beta 2 with 2019 support, so that people can give it a go. There's still time before the 1.70 release for another beta, but this creates extra work for the release manager, so it would be his call.
The result of https://www.boost.org/development/tests/develop/developer/summary.html for 14.2RC look good and green enough to me to make it very useful to merge to master before the release (with sympathy for the long-suffering release manager). With Microsoft providing so frequent updates, I suspect that any changes from the first VS 14.2 release will be small, and anyway will be followed by lots more quick bug fixes discovered by user's 'testing'. Getting master from GIT is different enough to deter many users, so we will please more people by releasing Boost with VS 2019 support. My two-pennyworth. Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
On Thu, Mar 14, 2019 at 9:21 AM Paul A. Bristow via Boost < boost@lists.boost.org> wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Peter Dimov via Boost Sent: 14 March 2019 14:25 To: boost@lists.boost.org Cc: Peter Dimov Subject: Re: [boost] MSVC 2019 and 1.70 beta
Tom Kent wrote:
Build support for VS 2019 RC (msvc-14.2) is on develop in boost build. Do we want to merge that to master for the release?
Taking all release dates into account, I think that the right thing to do would be to release Beta 2 with 2019 support, so that people can give it a go. There's still time before the 1.70 release for another beta, but this creates extra work for the release manager, so it would be his call.
The result of https://www.boost.org/development/tests/develop/developer/summary.html for 14.2RC look good and green enough to me to make it very useful to merge to master before the release (with sympathy for the long-suffering release manager).
If people think that the VS 2019 is ready to release, then I have no objection to putting it into the 1.70 release. However, I'd appreciate it if people kept an eye on the CI results and the test runners between now and the 3rd. -- Marshall
AMDG On 3/15/19 8:32 AM, Marshall Clow via Boost wrote:
On Thu, Mar 14, 2019 at 9:21 AM Paul A. Bristow via Boost < boost@lists.boost.org> wrote:
The result of https://www.boost.org/development/tests/develop/developer/summary.html for 14.2RC look good and green enough to me to make it very useful to merge to master before the release (with sympathy for the long-suffering release manager).
If people think that the VS 2019 is ready to release, then I have no objection to putting it into the 1.70 release. However, I'd appreciate it if people kept an eye on the CI results and the test runners between now and the 3rd.
I just merged the changes. In Christ, Steven Watanabe
On Thu, Mar 14, 2019 at 10:48 AM degski <degski@gmail.com> wrote:
On Thu, 14 Mar 2019 at 10:25, Olaf van der Spek via Boost <boost@lists.boost.org> wrote:
Is 2019 not properly supported yet?
It's not released yet
[i.e. it's a moving target],
It's RC, so it's not a moving target.
so seems normal to me.
I don't agree. -- Olaf
On Thu, 14 Mar 2019 at 12:58, Olaf van der Spek <ml@vdspek.org> wrote:
On Thu, Mar 14, 2019 at 10:48 AM degski <degski@gmail.com> wrote:
On Thu, 14 Mar 2019 at 10:25, Olaf van der Spek via Boost <
boost@lists.boost.org> wrote:
Is 2019 not properly supported yet?
It's not released yet
[i.e. it's a moving target],
It's RC, so it's not a moving target.
There could be RC2, RC3, etc etc ... I don't agree.
You think boost should support RC's? degski -- *"Big boys don't cry" - **Eric Stewart, Graham Gouldman*
On Thu, 14 Mar 2019 at 14:17, Olaf van der Spek <ml@vdspek.org> wrote:
It's silly to ignore MSVC until it's released as GA / RTM / RTW / whatever.
No, it's not, in the same sense that any question/problem arising from somebody using a Boost RC in production would be met by: "Install Release first." Whether a Boost Release could/should be coordinated with a VC Release is a totally other question (Peter seems to raise that), though (I think it should). degski -- *"Big boys don't cry" - **Eric Stewart, Graham Gouldman*
On Thu, Mar 14, 2019 at 1:37 PM degski <degski@gmail.com> wrote:
On Thu, 14 Mar 2019 at 14:17, Olaf van der Spek <ml@vdspek.org> wrote:
It's silly to ignore MSVC until it's released as GA / RTM / RTW / whatever.
No, it's not,
Why?
in the same sense that any question/problem arising from somebody using a Boost RC in production would be met by: "Install Release first."
If you want to reason by analogy, don't forget to include why you believe the two cases are equivalent.
Whether a Boost Release could/should be coordinated with a VC Release is a totally other question (Peter seems to raise that), though (I think it should).
IMO if you started preparing in December (after the preview release) probably no adjustments / coordination would've been needed. -- Olaf
participants (7)
-
degski -
Marshall Clow -
Olaf van der Spek -
Paul A. Bristow -
Peter Dimov -
Steven Watanabe -
Tom Kent