You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\Build\vcvarsamd64_x86.bat"
(Note, this is different from the line specified in the instructions for regular VC builds. It is tailored to the limited installation of BuildTools.)
python build_tools/build_qt.py --release --confirm_license
This is where it gets in trouble.
Error logs
extracting util/xkbdatagen/xkbdatagen.pro Traceback (most recent call last):
File "C:\Development\mozc\src\build_tools\build_qt.py", line 541, in <module>
main()
File "C:\Development\mozc\src\build_tools\build_qt.py", line 537, in main
build_on_windows(args)
File "C:\Development\mozc\src\build_tools\build_qt.py", line 437, in build_on_windows
env = get_vs_env_vars('amd64_x86', args.vcvarsall_path)
File "C:\Development\mozc\src\build_tools\build_qt.py", line 396, in get_vs_env_vars
vcvarsall = get_vcvarsall(vcvarsall_path_hint)
File "C:\Development\mozc\src\build_tools\build_qt.py", line 354, in get_vcvarsall
raise FileNotFoundError('Could not find vcvarsall.bat')
FileNotFoundError: Could not find vcvarsall.bat
Additional context
Yes, I examined the file build_qt.py near line 354. The function get_vcvarsall searches for vcvarsall.bat in standard editions of Visual Studio, but it does not seem to have any provision for a Visual Studio BuildTools installation.
Part of the code looks like this:
for edition in ['Community', 'Professional', 'Enterprise']:
vcvarsall = pathlib.Path('C:\\', 'Program Files', 'Microsoft Visual Studio',
'2022', edition, 'VC', 'Auxiliary', 'Build',
'vcvarsall.bat')
if vcvarsall.exists():
return vcvarsall
raise FileNotFoundError('Could not find vcvarsall.bat')
In my local copy, I added this before the raise statement, and it seemed to compile correctly after that:
# Also check for BuildTools, which is a smaller installation.
program_files_x86 = 'Program Files (x86)'
edition = 'BuildTools'
vcvarsall = pathlib.Path('C:\\', program_files_x86, 'Microsoft Visual Studio',
'2022', edition, 'VC', 'Auxiliary', 'Build',
'vcvarsall.bat')
if vcvarsall.exists():
return vcvarsall
The fresh VS 2020 BuildTools installation put itself in "Program Files (x86)" instead of Program Files. I don't know whether this is normal, or whether it's because I have some older installations of VS (2017 and 2019). However, in any case, the python code is not looking for a BuildTools installation.
Build instructions for Windows say that Build Tools for Visual Studio 2022 should work in place of the full installation of VS 2022:
"Build Tools for Visual Studio 2022 should also work"
This may be a small issue, but I appreciate your consideration.
The text was updated successfully, but these errors were encountered:
Coincidentally we recently submitted c777896 for our internal build servers where Build Tools for Visual Studio 2022 are installed in C:\VS\VC. With that I guess it's already possible for you to work around your case without changing the source code as follow.
Description
The QT dependencies fail to compile on Windows 10, when using Build Tools in place of a full Visual Studio 2022 installation.
Commit-id
88fb0c6
Build target
CI build status
Environment
Build commands
Steps of command lines to reproduce your error.
(Starting in folder C:\Development )
(Note, this is different from the line specified in the instructions for regular VC builds. It is tailored to the limited installation of BuildTools.)
This is where it gets in trouble.
Error logs
Additional context
Yes, I examined the file build_qt.py near line 354. The function get_vcvarsall searches for vcvarsall.bat in standard editions of Visual Studio, but it does not seem to have any provision for a Visual Studio BuildTools installation.
Part of the code looks like this:
In my local copy, I added this before the raise statement, and it seemed to compile correctly after that:
The fresh VS 2020 BuildTools installation put itself in "Program Files (x86)" instead of Program Files. I don't know whether this is normal, or whether it's because I have some older installations of VS (2017 and 2019). However, in any case, the python code is not looking for a BuildTools installation.
Build instructions for Windows say that Build Tools for Visual Studio 2022 should work in place of the full installation of VS 2022:
"Build Tools for Visual Studio 2022 should also work"
This may be a small issue, but I appreciate your consideration.
The text was updated successfully, but these errors were encountered: