Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Building QT6 from Source failed (qtbase printsupport_autogen\timestamp)
Forum Updated to NodeBB v4.3 + New Features

Building QT6 from Source failed (qtbase printsupport_autogen\timestamp)

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
19 Posts 9 Posters 3.2k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • joborJ Offline
    joborJ Offline
    jobor
    wrote on last edited by
    #2

    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_PatrickB 1 Reply Last reply
    0
    • joborJ 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_PatrickB Offline
      BDC_PatrickB Offline
      BDC_Patrick
      wrote on last edited by BDC_Patrick
      #3

      @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?

      1 Reply Last reply
      0
      • SGaistS Offline
        SGaistS Offline
        SGaist
        Lifetime Qt Champion
        wrote on last edited by
        #4

        Hi,

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

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        BDC_PatrickB 1 Reply Last reply
        0
        • SGaistS SGaist

          Hi,

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

          BDC_PatrickB Offline
          BDC_PatrickB Offline
          BDC_Patrick
          wrote on last edited by BDC_Patrick
          #5

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

          Error.jpg

          [....]
          
          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...

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #6

            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.

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            BDC_PatrickB 1 Reply Last reply
            0
            • SGaistS 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_PatrickB Offline
              BDC_PatrickB Offline
              BDC_Patrick
              wrote on last edited by
              #7

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

              jsulmJ 1 Reply Last reply
              0
              • BDC_PatrickB BDC_Patrick

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

                jsulmJ Online
                jsulmJ Online
                jsulm
                Lifetime Qt Champion
                wrote on last edited by
                #8

                @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

                https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply
                0
                • BDC_PatrickB Offline
                  BDC_PatrickB Offline
                  BDC_Patrick
                  wrote on last edited by
                  #9

                  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?

                  jsulmJ SGaistS 2 Replies Last reply
                  0
                  • BDC_PatrickB 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?

                    jsulmJ Online
                    jsulmJ Online
                    jsulm
                    Lifetime Qt Champion
                    wrote on last edited by
                    #10

                    @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...

                    https://forum.qt.io/topic/113070/qt-code-of-conduct

                    BDC_PatrickB 1 Reply Last reply
                    0
                    • BDC_PatrickB 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?

                      SGaistS Offline
                      SGaistS Offline
                      SGaist
                      Lifetime Qt Champion
                      wrote on last edited by
                      #11

                      @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_PatrickB 1 Reply Last reply
                      0
                      • jsulmJ 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...

                        BDC_PatrickB Offline
                        BDC_PatrickB Offline
                        BDC_Patrick
                        wrote on last edited by
                        #12

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

                        1 Reply Last reply
                        0
                        • SGaistS 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_PatrickB Offline
                          BDC_PatrickB Offline
                          BDC_Patrick
                          wrote on last edited by
                          #13

                          @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..?

                          jsulmJ 1 Reply Last reply
                          0
                          • BDC_PatrickB 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..?

                            jsulmJ Online
                            jsulmJ Online
                            jsulm
                            Lifetime Qt Champion
                            wrote on last edited by
                            #14

                            @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!).

                            https://forum.qt.io/topic/113070/qt-code-of-conduct

                            1 Reply Last reply
                            0
                            • D Offline
                              D Offline
                              dreckeffekt
                              wrote on last edited by
                              #15

                              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 ?

                              1 Reply Last reply
                              0
                              • N Offline
                                N Offline
                                Niyas Sait
                                wrote on last edited by
                                #16

                                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

                                1 Reply Last reply
                                0
                                • M Offline
                                  M Offline
                                  maisoui
                                  wrote on last edited by
                                  #17

                                  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

                                  1 Reply Last reply
                                  0
                                  • H Offline
                                    H Offline
                                    habersaa
                                    wrote on last edited by
                                    #18

                                    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 ?

                                    1 Reply Last reply
                                    0
                                    • A Offline
                                      A Offline
                                      avautour
                                      wrote on last edited by
                                      #19

                                      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.

                                      1 Reply Last reply
                                      0

                                      • Login

                                      • Login or register to search.
                                      • First post
                                        Last post
                                      0
                                      • Categories
                                      • Recent
                                      • Tags
                                      • Popular
                                      • Users
                                      • Groups
                                      • Search
                                      • Get Qt Extensions
                                      • Unsolved