Re: [boost] [Boost-build] Building Boost 1.69 with Visual Studio 1.69
AMDG On 3/27/19 12:02 PM, Paul Bristow wrote:
<snip> I was fully up-to-date on develop yesterday, and installed git a week ago (new machine ;-) ).
The current revision of Boost.Build in develop should be e22a75c8 (March 18)
I am also slightly concerned that specifying the cl.exe fully may not be updated when Visual studio is updated, as happens today? But it does seem to using the new compiler version, even though the full cl.exe file specification is no longer correct. Similarly vsvarsall.bat location in the set command will change.
But I am getting Boost library files built OK for several compilers and versions, so that's progress.
Hmm. It looks like VS2019 isn't being autodetected. It seems to be working for Tom's test runners. Maybe see what you get from: vswhere -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath -version "[16.0,17.0)" (This is how Boost.Build tries to detect VS2019.) In Christ, Steven Watanabe
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe via Boost Sent: 27 March 2019 18:56 To: Boost Cc: Steven Watanabe Subject: Re: [boost] [Boost-build] Building Boost 1.69 with Visual Studio 1.69
AMDG
On 3/27/19 12:02 PM, Paul Bristow wrote:
<snip> I was fully up-to-date on develop yesterday, and installed git a week ago (new machine ;-) ).
The current revision of Boost.Build in develop should be e22a75c8 (March 18)
I am also slightly concerned that specifying the cl.exe fully may not be updated when Visual studio is updated, as happens today? But it does seem to using the new compiler version, even though the full cl.exe file specification is no longer correct. Similarly vsvarsall.bat location in the set command will change.
But I am getting Boost library files built OK for several compilers and versions, so that's progress.
Hmm. It looks like VS2019 isn't being autodetected. It seems to be working for Tom's test runners.
Maybe see what you get from:
vswhere -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath -version "[16.0,17.0)"
(This is how Boost.Build tries to detect VS2019.)
I don't think that vswhere.exe is visible from my user or VS command prompts :-( C:\Users\Paul>C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe 'C:\Program' is not recognized as an internal or external command, operable program or batch file. C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional>vswhere.exe 'vswhere.exe' is not recognized as an internal or external command, operable program or batch file. C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview>vswhere.exe 'vswhere.exe' is not recognized as an internal or external command, operable program or batch file. But one copy is present at C:\Program Files (x86)\Microsoft Visual Studio\Installer and With no parameters vswhere outputs this C:\Users\Paul>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" Visual Studio Locator version 2.6.7+91f4c1d09e [query version 2.0.2250.60958] Copyright (C) Microsoft Corporation. All rights reserved. instanceId: bd686eb9 installDate: 10Dec2018 16:18:55 installationName: VisualStudio/15.9.10+28307.557 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional installationVersion: 15.9.28307.557 productId: Microsoft.VisualStudio.Product.Professional productPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe state: 4294967295 isComplete: 1 isLaunchable: 1 isPrerelease: 0 isRebootRequired: 0 displayName: Visual Studio Professional 2017 description: Professional developer tools and services for small teams channelId: VisualStudio.15.Release channelUri: https://aka.ms/vs/15/release/channel enginePath: C:\program files (x86)\microsoft visual studio\installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service releaseNotes: https://go.microsoft.com/fwlink/?LinkId=660692#15.9.10 thirdPartyNotices: https://go.microsoft.com/fwlink/?LinkId=660708 updateDate: 2019-03-27T11:37:49.0677562Z catalog_buildBranch: d15.9 catalog_buildVersion: 15.9.28307.557 catalog_id: VisualStudio/15.9.10+28307.557 catalog_localBuild: build-lab catalog_manifestName: VisualStudio catalog_manifestType: installer catalog_productDisplayVersion: 15.9.10 catalog_productLine: Dev15 catalog_productLineVersion: 2017 catalog_productMilestone: RTW catalog_productMilestoneIsPreRelease: False catalog_productName: Visual Studio catalog_productPatchVersion: 10 catalog_productPreReleaseMilestoneSuffix: 1.0 catalog_productRelease: RTW catalog_productSemanticVersion: 15.9.10+28307.557 catalog_requiredEngineVersion: 1.18.1049.33485 properties_campaignId: 1028583927.1544458409 properties_channelManifestId: VisualStudio.15.Release/15.9.10+28307.557 properties_nickname: properties_setupEngineFilePath: C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installershell.exe running his with the options you give produced NO output: C:\Program Files (x86)\Microsoft Visual Studio\Installer>vswhere.exe -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath -version "[16.0,17.0)" I'm installing some other Visual Studio items to see if that will help. I conclude that you are correct but what is wrong with my install is as yet unclear to me. https://devblogs.microsoft.com/setup/vswhere-is-now-installed-with-visual-st... dated in 2017 suggests that vswhere.exe should have been present using VS2017. Do I just need vswhere.exe in my path? Thanks for yet more help. Paul
AMDG On 3/28/19 9:30 AM, Paul A. Bristow via Boost wrote:
<snip> I don't think that vswhere.exe is visible from my user or VS command prompts :-(
<snip>
But one copy is present at C:\Program Files (x86)\Microsoft Visual Studio\Installer and
That's the right one.
With no parameters vswhere outputs this
C:\Users\Paul>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" Visual Studio Locator version 2.6.7+91f4c1d09e [query version 2.0.2250.60958] Copyright (C) Microsoft Corporation. All rights reserved.
instanceId: bd686eb9 installDate: 10Dec2018 16:18:55 installationName: VisualStudio/15.9.10+28307.557 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional installationVersion: 15.9.28307.557 <snip>
I'm installing some other Visual Studio items to see if that will help.
I conclude that you are correct but what is wrong with my install is as yet unclear to me.
https://devblogs.microsoft.com/setup/vswhere-is-now-installed-with-visual-st...
dated in 2017 suggests that vswhere.exe should have been present using VS2017.
Do I just need vswhere.exe in my path?
That won't affect Boost.Build. msvc.jam knows where to find vswhere. In Christ, Steven Watanabe
On Thu, 28 Mar 2019 at 17:49, Steven Watanabe via Boost < boost@lists.boost.org> wrote:
C:\Users\Paul>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" Visual Studio Locator version 2.6.7+91f4c1d09e [query version 2.0.2250.60958] Copyright (C) Microsoft Corporation. All rights reserved.
With only VS/15.9.10 installed I get: C:\Program Files (x86)\Microsoft Visual Studio\Installer>vswhere.exe Visual Studio Locator version 2.5.2+gebb9f26a3d [query version 1.18.21.37008] Copyright (C) Microsoft Corporation. All rights reserved. So it appears to be a newer (VS2019) version. It's not in my path either, from any prompt. degski -- *Microsoft, please kill Paint3D*
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe via Boost Sent: 28 March 2019 15:50 To: Paul A. Bristow via Boost Cc: Steven Watanabe Subject: Re: [boost] [Boost-build] Building Boost 1.69 with Visual Studio 1.69
AMDG
On 3/28/19 9:30 AM, Paul A. Bristow via Boost wrote:
<snip> I don't think that vswhere.exe is visible from my user or VS command prompts :-(
<snip>
But one copy is present at C:\Program Files (x86)\Microsoft Visual Studio\Installer and
That's the right one.
With no parameters vswhere outputs this
C:\Users\Paul>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" Visual Studio Locator version 2.6.7+91f4c1d09e [query version 2.0.2250.60958] Copyright (C) Microsoft Corporation. All rights reserved.
instanceId: bd686eb9 installDate: 10Dec2018 16:18:55 installationName: VisualStudio/15.9.10+28307.557 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional installationVersion: 15.9.28307.557 <snip>
I'm installing some other Visual Studio items to see if that will help.
It didn't. But I did notice that vswhere does not find vs2019 at all with the option -all, but vswhere *does* find both VS2017 and VS2019 with -prerelease option. So have I jumped the gun by prematurely installing the preview? Does msvc.jam need this adding to the list of options? I:\modular-boost\tools\build\src\tools\msvc.jam local vmwhere_cmd = "\"$(vswhere)\" -latest -products * $(req) $(prop) $(limit)" ; perhaps? but there are also some assumptions about 15.0 builtin, so perhaps I am entering where angels fear to tread. (assuming it is agreed that we want to find preview versions?) Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
On Fri, 29 Mar 2019 at 12:21, Paul A. Bristow via Boost < boost@lists.boost.org> wrote:
But I did notice that vswhere does not find vs2019 at all with the option -all,
but vswhere *does* find both VS2017 and VS2019 with -prerelease option.
It all makes sense in my mind. Until VS2019 goes RTM it's not recognised, unless you specifically ask for it. This means up till that moment, all default builds will use the latest RTM, which is VS2017. From a corporate perspective this makes a lot of sense, nobody wants accidents. I've said this before, until it [VS2019] goes RTM it's as a matter of principle unstable. So have I jumped the gun by prematurely installing the preview?
Yes and no, I would say. degski -- *Microsoft, please kill Paint3D*
Paul A. Bristow wrote:
So have I jumped the gun by prematurely installing the preview?
Which VS2019 have you installed? You want the RC from this page: https://visualstudio.microsoft.com/downloads/ not the preview from this one: https://visualstudio.microsoft.com/vs/preview/
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Peter Dimov via Boost Sent: 29 March 2019 13:36 To: boost@lists.boost.org Cc: Peter Dimov Subject: Re: [boost] [Boost-build] Building Boost 1.69 with Visual Studio 1.69
Paul A. Bristow wrote:
So have I jumped the gun by prematurely installing the preview?
Which VS2019 have you installed? You want the RC from this page:
https://visualstudio.microsoft.com/downloads/
not the preview from this one:
Now you tell me :-( I can think I can contain my enthusiasm until the actually launch on 2 April. But thanks, I am sure that you are right. Paul PS This still leaves unsolved of whether bjam/b2 should find preview versions 'automatically', or like vswhere default, ignore their existence. I don't think that Boost should make it difficult to check out previews. --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
On Fri, 29 Mar 2019 at 16:23, Paul A. Bristow via Boost < boost@lists.boost.org> wrote:
I can think I can contain my enthusiasm until the actually launch on 2 April.
Make up your own mind: https://www.zdnet.com/article/microsoft-officially-designates-windows-10-180... . The next Windows update is (I'm guessing here) slated for 9th of April, and now we declare 1809 ready for broad deployment, yes, all good stuff. That leaves some question marks. degski -- *Microsoft, please kill Paint3D*
Paul A. Bristow wrote:
Which VS2019 have you installed? You want the RC from this page:
https://visualstudio.microsoft.com/downloads/
not the preview from this one:
Now you tell me :-(
I can think I can contain my enthusiasm until the actually launch on 2 April.
Sorry. :-) FWIW, the RC will update itself automatically on Apr 2. So it shouldn't matter whether you install it now or then, you ought to end up at the same place. https://devblogs.microsoft.com/visualstudio/visual-studio-2019-release-candi...
Am 29.03.2019 um 11:21 schrieb Paul A. Bristow via Boost-build:
With no parameters vswhere outputs this
C:\Users\Paul>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" Visual Studio Locator version 2.6.7+91f4c1d09e [query version 2.0.2250.60958] Copyright (C) Microsoft Corporation. All rights reserved.
instanceId: bd686eb9 installDate: 10Dec2018 16:18:55 installationName: VisualStudio/15.9.10+28307.557 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional installationVersion: 15.9.28307.557 <snip>
I'm installing some other Visual Studio items to see if that will help.
It didn't.
But I did notice that vswhere does not find vs2019 at all with the option -all,
Well, on my machine with VS2019.RC4 and VS2017.Buildtools (replaces VS2017.9, one IDE is enough) installed, vswhere picks up only VS2019: instanceId: b1b66fa0 installDate: 24.03.2019 17:14:45 installationName: VisualStudio/16.0.0+28721.148.rc.4 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional installationVersion: 16.0.28721.148 Microsoft's Visual Studio installer shows both installed SKUs though. Ciao Dani
On Fri, Mar 29, 2019 at 10:33 AM Daniela Engert via Boost < boost@lists.boost.org> wrote:
Am 29.03.2019 um 11:21 schrieb Paul A. Bristow via Boost-build:
With no parameters vswhere outputs this
C:\Users\Paul>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" Visual Studio Locator version 2.6.7+91f4c1d09e [query version 2.0.2250.60958] Copyright (C) Microsoft Corporation. All rights reserved.
instanceId: bd686eb9 installDate: 10Dec2018 16:18:55 installationName: VisualStudio/15.9.10+28307.557 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional installationVersion: 15.9.28307.557 <snip>
I'm installing some other Visual Studio items to see if that will help.
It didn't.
But I did notice that vswhere does not find vs2019 at all with the option -all,
Well, on my machine with VS2019.RC4 and VS2017.Buildtools (replaces VS2017.9, one IDE is enough) installed, vswhere picks up only VS2019:
instanceId: b1b66fa0 installDate: 24.03.2019 17:14:45 installationName: VisualStudio/16.0.0+28721.148.rc.4 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional installationVersion: 16.0.28721.148
Microsoft's Visual Studio installer shows both installed SKUs though.
On my machine (msvc-10.0, 11.0, 12.0, 14.0, 14.1, 14.2) I get the following from vswhere: C:\Users\tomkent>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -products * -property InstallationName VisualStudio/16.0.0+28721.148.rc.4 VisualStudio/15.9.10+28307.557 C:\Users\tomkent>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -products * -property displayName Visual Studio Build Tools 2019 Visual Studio Enterprise 2017 C:\Users\tomkent>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -products * -property InstallationPath C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise Tom
Am 29.03.2019 um 19:00 schrieb Tom Kent via Boost:
C:\Users\tomkent>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -products * -property InstallationPath C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
Ah, I see: the '-products *' part is the secret sauce! Thanks! Now I get vswhere.exe -products * -legacy -property InstallationPath C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional C:\Program Files (x86)\Microsoft Visual Studio 14.0\ C:\Program Files (x86)\Microsoft Visual Studio 12.0\ C:\Program Files (x86)\Microsoft Visual Studio 11.0\ C:\Program Files (x86)\Microsoft Visual Studio 10.0\ VS2019 is with ide, everything else are just the bare build tools. It doesn't pick up VS2008 which is also installed, but that's ok: I'm probably asking for a little too much :-) Ciao Dani
participants (6)
-
Daniela Engert -
degski -
Paul A. Bristow -
Peter Dimov -
Steven Watanabe -
Tom Kent