Building QT6 from Source failed (qtbase printsupport_autogen\timestamp)

BDC_Patrick

Hi there..

I´m fairly new in building stuff from source... but i need to in order to use QT with LGPL License...

So i follow the Manual here: link Building QT6 from Source
Using Windows10 (64Bit)

And everytime end up with this:

So.. Can someone help me out here?

jobor

Hi, what's your CMake version and your exact configure line?

Also, you don't need to build Qt from source to use the LGPL license.

BDC_Patrick

@jobor I followed this page exactly:
https://wiki.qt.io/Building_Qt_6_from_Git

cmake is installed via msys mingw and is v3.20
latest perl and Python are on, too.

config is simple:
configure -prefix D:\QT6

build start with:
cmake --build . --parallel

What is needed to fulfill the LGPL License?

SGaist

Hi,

I do not currently what triggered the error, can you restart the build single threaded to see the point of error ?

BDC_Patrick

@SGaist Sure..
Here is the complete log on a fresh clone from start to fail (with parallel set to 1):
Pastebin.com Link

[....]

D:\QT_Source\qt5\qt6-build>cmake --build . --parallel 1
[841/5164] Automatic MOC for target Sql
FAILED: qtbase/src/sql/Sql_autogen/timestamp
cmd.exe /C "cd /D D:\QT_Source\qt5\qt6-build\qtbase\src\sql && C:\msys64\mingw64\bin\cmake.exe -E cmake_autogen D:/QT_Source/qt5/qt6-build/qtbase/src/sql/CMakeFiles/Sql_autogen.dir/AutogenInfo.json Release && C:\msys64\mingw64\bin\cmake.exe -E touch D:/QT_Source/qt5/qt6-build/qtbase/src/sql/Sql_autogen/timestamp && C:\msys64\mingw64\bin\cmake.exe -E cmake_transform_depfile Ninja gccdepfile D:/QT_Source/qt5 D:/QT_Source/qt5/qtbase/src/sql D:/QT_Source/qt5/qt6-build D:/QT_Source/qt5/qt6-build/qtbase/src/sql D:/QT_Source/qt5/qt6-build/qtbase/src/sql/Sql_autogen/deps D:/QT_Source/qt5/qt6-build/CMakeFiles/d/528de724a04ac3a914ace0f1df615f542b4d0c8c8de1c3e9d0482d385f1df276.d"
ninja: build stopped: subcommand failed.

It seems like it failes on different positions...

SGaist

I do not say it's related to that but I would rather go with the MinGW version provided by the online installer which should match the one used for the Qt MinGW build.

BDC_Patrick

@SGaist What do you mean exactly?
As said, I'm relatively new to building things with cmd/shell..

jsulm

@BDC_Patrick said in Building QT6 from Source failed (qtbase printsupport_autogen\timestamp):

What do you mean exactly?

Use MinGW wich you can install (probably already installed) through Qt Online Installer (or Qt Maintenance Tool) instead of C:\msys64\mingw64

BDC_Patrick

Yes.. i´ve installed QT6 Creator..

So.. you said, that i don´t need to build it from Source to be used under LGPL..
But, how to give the Users the Source after finishing.. is it stored locally somewhere in the QT Directories?

jsulm

@BDC_Patrick said in Building QT6 from Source failed (qtbase printsupport_autogen\timestamp):

So.. you said, that i don´t need to build it from Source

Where?
All I said (actually @SGaist) is that you should use MinGW provided through Qt Online Installer/Qt Maintenance Tool...

SGaist

@BDC_Patrick said in Building QT6 from Source failed (qtbase printsupport_autogen\timestamp):

Yes.. i´ve installed QT6 Creator..

So.. you said, that i don´t need to build it from Source to be used under LGPL..
But, how to give the Users the Source after finishing.. is it stored locally somewhere in the QT Directories?

There never was such a restriction.

The online installer already provides Qt 6 pre-built binaries.

BDC_Patrick

@jsulm Yeah.. it was @jobor , my mistake.

BDC_Patrick

@SGaist OK.. to be clear.. cause those license Stuff is beyond a normal human beings context.. :

To fulfill the LGPL License, the binary QT (without Virt. Keyboard, Charts, Data Viz.. is absolutely OK..? Am I right there?
What about the Source offering?

And most: what if I want to keep my Application code private.. and not. open source..?

jsulm

@BDC_Patrick LGPL is fine for closed source software. You only have to open source your changes to Qt itself if you do any. And you have to make sure users of your software can relink your softwareagainst their own Qt builds (easy if you use shared libs, for static builds you need to provide object files, but not source code!).

dreckeffekt

Hi, I know this topic is quite old but I'm currently having the same issue (I'm also quite new when it comes to all of this).

I get the same error at different steps in the build, so the module does not seem to matter, but it always fails at a [some module]_autogen\timestamp.
While I'll have to confirm this, I think this might have something to do with the ninja multi-config generator that's used when setting the '-debug-and-release' flag on configure.bat, as this doesn't seem to happen when only building for Release configuration. Does anyone have a fix for this or did switching the compiler work for you @BDC_Patrick ?

Niyas Sait

Hi, I am running into the same issue, Is there any solution for this?

My Environment:

Host and Target: Windows 11 / Arm64 ( Surface Pro)
Compiler: MSVC v142
Commit: Tag v6.2.3 and a9c9418c(dev HEAD)
CMake: 3.21.4
Python: 3.10.0
Ninja: 1.10.2

maisoui

Hi,

same problem here. I tried unsuccessfully different versions of CMAKE.
Has anyone found the solution? I really need to build Qt from sources.

Regards

habersaa

Hey.
We are experiencing the same issues with ninja and MSVC2019, but on another big Qt/QML project that we are building with Qt 6.6.0. On the CI, one every 3-5 build fails with this error related to timestamp.

Do anyone have an idea how to debug/avoid this issue ?

avautour

I know this is an old post, but I figured I'd add this information as I ran into it.

I don't think it is related to autogen or timestamps, I believe it is related to precompiled header files in general, because some of the failures I ran into had nothing to do with autogen, even thought some of them did:

/Fdqtbase\src\openglwidgets\CMakeFiles\OpenGLWidgets.dir\ /FS -c qtbase\src\openglwidgets\CMakeFiles\OpenGLWidgets.dir\cmake_pch.cxx Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30153 for x64 Copyright (C) Microsoft Corporation. All rights reserved. ninja: build stopped: subcommand failed.

11:55:53 [836/4092] Building CXX object qtlanguageserver\src\jsonrpc\CMakeFiles\JsonRpcPrivate.dir\cmake_pch.cxx.obj 11:55:53 [837/4092] Building CXX object qtgrpc\src\protobuf\CMakeFiles\Protobuf.dir\cmake_pch.cxx.obj 11:55:53 [838/4092] Building CXX object qtserialport\src\serialport\CMakeFiles\SerialPort.dir\cmake_pch.cxx.obj 11:55:53 [839/4092] Building CXX object qtconnectivity\src\nfc\CMakeFiles\Nfc.dir\cmake_pch.cxx.obj 11:55:53 ninja: build stopped: subcommand failed.

I was able to work-around it by disabling precompiled headers files by adding -DCMAKE_DISABLE_PRECOMPILE_HEADERS=ON to the CMake generation step. I was using the CMake with Visual Studio 2019 ( 3.20.21032501-MSVC_2) on Qt 6.7.3.