Trying to build qt 5.15.14 x64 on windows.

Christian Ehrlicher

You have to open the amd64 x64 visual studio prompt and start over with a clean build dir.

james b-s

Doesn't C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\vcvars64 do the same thing?

Christian Ehrlicher

Don't know, make sure 'where cl.exe' returns the correct compiler.

james b-s

I'm trying your suggestion, but I don't think it will make a difference. It will take 2 hours before I know.
Where cl gives
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.28.29910\bin\Hostx64\x64\cl.exe
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.28.29910\bin\Hostx86\x86\cl.exe

C:\Qt\5.15>cl -version
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29913 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

I would think that there would be some switch to tell qt which to build, probably in the configure.bat command line.

I would also expect this to be documented somewhere.

Christian Ehrlicher

Why is also the 32bit compiler in the path? Use the correct visual studio command prompt.

james b-s

when I open the command prompt from within visual studio, I get this
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.34.31933\bin\Hostx86\x86\cl.exe

That doesn't seem any better

I found some stuff online for qt6 (I'm building qt5) that says that this:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary\Build\vcvars64
is the correct way to set the symbols. That's what I was doing. I'm trying the from the visual studio command line, but it will take a while.

james b-s

I'm trying cleaning everything by deleting the directory qt produced (nmake clean doesn't get rid of everything). I restarted everything. where cl only lists the one compiler. cl lists the right compiler. I'll let you know in 2 hours

Christian Ehrlicher

Just take a look in the task manager which cl.exe is used. Or look at QtCore.dll to see if it is a 64bit dll.

james b-s

This post is deleted!

james b-s

I have built the release build of Qt, but when I try to use it, I get a fatal program exit when QApplication is called, so now I am trying to build a debug build of Qt to see if I can get more information.

My configure command looks like this:
configure.bat -platform win32-msvc -opensource -debug -verbose
The output contains the following:
Mode ................................... debug; optimized tools

The build process creates library files like translator.lib, it does not create translatord.lib.

When I run "nmake install", I get
NMAKE : fatal error U1073: don't know how to make 'C:\Qt\5.15\qtbase\lib\translatord.lib'

There are some debug libraries in that directory, built today. There are also translator.prl and translatord.prl. Also built today

Christian Ehrlicher

Simply create debug and release in one build directory... - see configure.bat --help --> -debug-and-release

james b-s

I'm running the nmake command again, capturing the output. It seems to have built translatord.lib this time, but I do see a lot of errors like this

WARNING: Failure to find: qt5qmld_metatypes.json
WARNING: Failure to find: C:/Qt/5.15/qtdeclarative/src/3rdparty/masm/assembler/.h
WARNING: Failure to find: C:/Qt/5.15/qtdeclarative/src/3rdparty/masm/wtf/.h
WARNING: Failure to find: C:/Qt/5.15/qtdeclarative/src/qml/qt5qmld_metatypes.json
WARNING: Failure to find: C:/Qt/5.15/qtdeclarative/src/3rdparty/masm/assembler/.h
WARNING: Failure to find: C:/Qt/5.15/qtdeclarative/src/3rdparty/masm/wtf/.h
Cannot open foreign types file C:/Qt/Qt-5.15.14/lib/metatypes/qt5network_metatypes.json
WARNING: Failure to find: qt5qmlmodelsd_metatypes.json
WARNING: Failure to find: C:/Qt/5.15/qtdeclarative/src/qmlmodels/qt5qmlmodelsd_metatypes.json

paangele

James b-s have you succeeded building a 5.15.14 x64 windows msvc2022 build? I have tried the same, and while the build process completes, my build seems unable to run applications..