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? -
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?@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... -
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?@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.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct -
@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... -
@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.
@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..?
-
@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..?
@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!).
-
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 ? -
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 -
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 ?
-
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.
