Closed Bug 1235764 Opened 10 years ago Closed 10 years ago

vcvars32.bat not found when using Visual Studio 2015

Categories

(Calendar :: Build Config, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: phlsa, Unassigned)

References

Details

It seems that Visual Studio 2015 doesn't come with the vcvars32.bat file that mozilla-build expects. There is a similar file in a different location though that seems to work. From an answer on this page http://superuser.com/questions/944951/no-windows-sdk-found-when-installing-spidermonkey === On my VS 2015 (community edition), there is no vcvars32.bat, but there is a vsvars32.bat, located into\Common7\Tools folder. I've patched the mozilla-build\start-shell.bat from (line 107): IF EXIST "!VCDIR!\bin\vcvars32.bat" ( CALL "!VCDIR!\bin\vcvars32.bat" SET TOOLCHAIN=32-bit ) to: IF EXIST "!VCDIR!\..\Common7\Tools\vsvars32.bat" ( CALL "!VCDIR!\..\Common7\Tools\vsvars32.bat" SET TOOLCHAIN=32-bit ) === This has worked for me as well.
Weird. My VS2015 community edition does have vcvars32.bat on the location in start-shell.bat. Also, for me, it prefers the 64bit cross-compile toolchain above. Probably some of the necessary components are not installed?
The Windows build prerequisites page on MDN says: Be sure to install the C++ tools which requires a customized installation in Visual Studio 2015. So probably you want to add some components of your install.
I installed all items under Visual C++, as well as "Windows 10 SDK", "Tools and Windows 10 SDK" under "Universal Windows App Development Tools", and "Tools and Windows SDKs" under "Windows 8.1 and ...". I guess you didn't install all items under Visual C++ which causes this issue.
Oh, you are absolutely right. I didn't see the part about c++ tools being an optional setting in the VS installer. Repaired the install and it now works without the hack I mentioned.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Probably worth a more detailed record in the prerequisites page...
You need to log in before you can comment on or make changes to this bug.