[wix-devs] Building from the VS developer command prompt

[Bob Arnson]

That's just Dev15. I sincerely hope we never need to create multiple versions of native libraries for C++ v19.

But we do need to support previous releases of VS, at least as far back as we want to support in WiX v4...

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Heath Stewart
Sent: Monday, 10 July, 2017 18:24
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] Building from the VS developer command prompt

If you want to maintain a build-from-any-prompt environment, see https://blogs.msdn.microsoft.com/vcblog/2017/03/06/finding-the-visual-c-compiler-tools-in-visual-studio-2017/ - specifically "Identifying the VC+ compiler tools version" if you wanted to supported building under multiple.

Heath Stewart
Visual Studio, Microsoft
http://blogs.msdn.microsoft.com/heaths

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Bob Arnson
Sent: Monday, July 10, 2017 11:26 AM
To: wix-devs <wix-devs at lists.wixtoolset.org>
Subject: [wix-devs] Building from the VS developer command prompt

One of the problems we've run into with VS2017 is that not only are directories not centralized, many are now versioned and those versions have changed in the two updates that VS2017 has shipped so far. So I decided to look at building from a VS developer command prompt, letting it "find" the right paths for us, instead of the current approach of having the WiX build tools do the hunting. The downside is that if we do this, you won't be able to build WiX from any ol' command prompt. The upside is that I won't have to maintain a supported list of Windows SDKs forever.

I have a work-in-progress branch for building with the VS command prompt at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbarnson%2Fwix4%2Ftree%2Fvs_dev_command_prompt&data=02%7C01%7CHeath.Stewart%40microsoft.com%7C1189fabba44f42d92d8a08d4c7c11977%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636353079646694630&sdata=9s2DG%2B6JebfkK8pFv0RumUSej%2Bs0g9oyv1JIqK2xRUk%3D&reserved=0. More work to do but that branch currently builds all of WiX on VS2017. But right now, I don't have a machine with multiple versions of VS installed, so:

1. I don't know if this broke multitargeting for *Util native libraries.
2. I don't know if this approach works with other versions of the VS command prompt.

Anybody with spare time and a machine with multiple VSes who could try out a build from my branch and report back? I have virtual cookies to share!
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.firegiant.com%2F&data=02%7C01%7CHeath.Stewart%40microsoft.com%7C1189fabba44f42d92d8a08d4c7c11977%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636353079646694630&sdata=DNdsCL4oSEO%2BoYfrSfqUJW5p%2BGJxIKBcHIxFDQC84EE%3D&reserved=0
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/