I have VS2015 Community update 3 installed with C++ tooling and the latest compatible Windows SDK.īefore this patch everything builds as expected using PCBuild\build.bat -e. The C++ tooling breaks other projects I'm working on. What is your system setup that causes this failure when you expect success?Ĭurrently I have VS2017 installed without C++ tooling for. You're going to get build failures without the C++ tooling anyway, and msbuild should find previous installs that are compatible.
Microsoft recommends using this tool to find and set up the paths, it also works with VS2015. This change causes build failures when VS2017 is installed without the C++ tooling as it finds MSBuild belonging to VS2017 but it can't build using it. Ned - this has been merged into 3.6 branch and the buildbots look good.įeel free to move the NEWS item around and/or cherrypick into 3.6.2 at your leisure. New changeset 2c899ccffda92a7f3d4e7a01f14a666504db07b5 by Steve Dower in branch '3.5':īpo-30687: Fixes build scripts to find msbuild.exe and stop relying on vcvarsall.bat ( #2252) ( #2281) New changeset 40a23e88994aca92c83c8e84ab8b8cdc11d7ec54 by Steve Dower in branch 'master':īpo-30687: Fixes build scripts to find msbuild.exe and stop relying on vcvarsall.bat ( #2252) We only require MSBuild.exe to build, so we should find that tool and invoke it, rather than trying to configure the entire environment.
Pull Requestsĭue to how installation of Visual Studio 2017 has changed, it's very possible to end up with a valid install of the build tools without vcvarsall.bat being valid.
Paxxi, jkloth, ned.deily, paul.moore, steve.dower, tim.golden, zach.wareĬreated on 22:03 by steve.dower, last changed 04:51 by ned.deily. Build.bat should locate msbuild.exe rather than vcvarsall.bat
0 kommentar(er)
