Building QT6.5 with NMake error
-
Hello all,
I am getting an error when building Qt6. It is getting stuck on qt6qml_debug_metatypes.json
Below is the output of the error:
Error 5 while parsing C:/Users/Phillip/source/qt6-build/qtdeclarative/src/qml/meta_types/qt6qml_debug_metatypes.json: illegal value NMAKE : fatal error U1077: 'call ..\..\..\.qt\bin\qt_setup_tool_path.bat C:/Users/Phillip/source/qt6-build/qtbase/bin/qmltyperegistrar.exe --generate-qmltypes=C:/Users/Phillip/source/qt6-build/qtbase/qml/QtQml/Base/plugins.qmltypes --import-name=QtQml.Base --major-version=6 --minor-version=5 --follow-foreign-versioning @C:/Users/Phillip/source/qt6-build/qtdeclarative/src/qml/qmltypes/Qml_foreign_types.txt --private-includes -o C:/Users/Phillip/source/qt6-build/qtdeclarative/src/qml/qml_qmltyperegistrations.cpp C:/Users/Phillip/source/qt6-build/qtdeclarative/src/qml/meta_types/qt6qml_debug_metatypes.json' : return code '0x1' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\bin\HostX86\x86\nmake.exe" -s -f qtdeclarative\src\qml\CMakeFiles\Qml.dir\build.make /nologo -SL qtdeclarative\src\qml\CMakeFiles\Qml.dir\depend' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\bin\HostX86\x86\nmake.exe" -s -f CMakeFiles\Makefile2 /nologo -S all' : return code '0x2' Stop.
When I go to the file qt6qml_debug_metatypes and open it, it is just a blank json file. There is nothing in it so I think that this is the issue as it is suppose to have contents in it.
Has anyone else ran into this issue before?
-
@Omni_Philm said in Building QT6.5 with NMake error:
qt6qml_debug_metatypes
Looks at lot like QTBUG-94942 from a few dot releases ago. Some changes were made to fix this in 2021.
-
I guess I will need to merge the changes for the specific files from the dev branch into the installation of 6.5.2 source to fix the issue?
-
@Omni_Philm According to the bug report it was fixed in 6.1.3
-
@Omni_Philm Maybe it is not the same issue as the one @ChrisW67 posted.