-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update instal script to delete any existing files.
- Loading branch information
Showing
1 changed file
with
2 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
510f890
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command line:
powershell.exe (Get-Command msbuild.exe)
returns this:
for me.
So this line:
powershell.exe -Command ((Get-Command msbuild.exe).Path ^| Split-Path -parent) > msbuild.txt
returns error, because,
powershell.exe (Get-Command msbuild.exe).Path
returns NULL.
So, this line works for me:
powershell.exe -Command ((Get-Command msbuild.exe)[0].Path ^| Split-Path -parent) > msbuild.txt
Also this line:
set VCTargetsPath="..\..\..\Microsoft.Cpp\v4.0\V%MSVC_VER%0"
is wrong.The correct line is:
set VCTargetsPath="..\..\Microsoft.Cpp\v4.0\V%MSVC_VER%0"
Because MSBUILDDIR = c:\Program Files (x86)\MSBuild\12.0\Bin
and path to BuildCustomizations is:
c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\BuildCustomizations\
510f890
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thats interesting as everywhere else ive seen MSBUILDDIR = c:\Program Files (x86)\MSBuild\12.0\Bin\amd64
as it runs by default in an x64 shell so the current VCTargetsPath works fine.
Ill have to investigate this further.
510f890
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be fixed in latest version (although the original worked in every 2013/2015/2017 install ive tested on anyway). But this should help fix your issue. If you have further problems create an issue ticket.