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. 5.12 shadow build not working

5.12 shadow build not working

Scheduled Pinned Locked Moved Solved Installation and Deployment
7 Posts 2 Posters 1.4k Views
  • 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.
  • T Offline
    T Offline
    Taytoo
    wrote on last edited by Taytoo
    #1

    I am able to do static build in sources folder, however, shadow building is not working. I've followed directions as listed on Qt 5.12 wiki, also tried instructions from several blogs online - same error:

            C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Release
            cd 3rdparty\pcre2\ && ( if not exist Makefile C:\Qt\Static\5.12.0_crt\qtbase\bin\qmake.exe -o Makefile C:\Qt\Sta
    tic\qt-everywhere-src-5.12.0\qtbase\src\3rdparty\pcre2\pcre2.pro ) && C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile
            C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Debug all
            C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Release all
            cd tools\moc\ && ( if not exist Makefile C:\Qt\Static\5.12.0_crt\qtbase\bin\qmake.exe -o Makefile C:\Qt\Static\q
    t-everywhere-src-5.12.0\qtbase\src\tools\moc\moc.pro ) && C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile
    Project ERROR: Unknown module(s) in QT: bootstrap-private
    jom: C:\Qt\Static\5.12.0_crt\qtbase\src\Makefile [sub-moc-make_first] Error 3
            cd tools\rcc\ && ( if not exist Makefile C:\Qt\Static\5.12.0_crt\qtbase\bin\qmake.exe -o Makefile C:\Qt\Static\q
    t-everywhere-src-5.12.0\qtbase\src\tools\rcc\rcc.pro ) && C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile
            cd tools\qfloat16-tables\ && ( if not exist Makefile C:\Qt\Static\5.12.0_crt\qtbase\bin\qmake.exe -o Makefile C:
    \Qt\Static\qt-everywhere-src-5.12.0\qtbase\src\tools\qfloat16-tables\qfloat16-tables.pro ) && C:\Qt\Tools\QtCreator\bin\
    jom.exe -f Makefile
    Project ERROR: Unknown module(s) in QT: bootstrap-private
    jom: C:\Qt\Static\5.12.0_crt\qtbase\src\Makefile [sub-rcc-make_first] Error 3
    Project ERROR: Unknown module(s) in QT: bootstrap-private
    jom: C:\Qt\Static\5.12.0_crt\qtbase\src\Makefile [sub-qfloat16-tables-make_first] Error 3
    jom: C:\Qt\Static\5.12.0_crt\qtbase\Makefile [sub-src-make_first] Error 2
    jom: C:\Qt\Static\5.12.0_crt\Makefile [module-qtbase-make_first] Error 2
    

    Note: the only thing I'm doing differently then what's on the qt wiki is not running qmake because makefiles are already generated by configure and it says at the end of configure output to use nmake or jom.

    MSVC 2017
    Windows 7 (64-bit)
    Qt 32-bit build

    1 Reply Last reply
    0
    • T Offline
      T Offline
      Taytoo
      wrote on last edited by
      #7

      In case anyone runs into the same problem. The fix was prefix path, you have to append \qtbase to whatever path you choose for shadow build folder.

      E.g. if you wanted shadow build in folder "c:\qt\static\5.12.1" then prefix would be "-prefix c:\qt\static\5.12.1\qtbase". The shadow build would still be in the "c:\qt\static\5.12.1" folder.

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

        Hi,

        Did you also provide a prefix in the configure options ?

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

        1 Reply Last reply
        0
        • T Offline
          T Offline
          Taytoo
          wrote on last edited by
          #3

          Yes. following is the exact command:

          C:\Qt\Static\5.12.0_crt>..\qt-everywhere-src-5.12.0\configure -commercial -static -debug-and-release -prefix C:\Qt\Static\5.12.0_crt -platform win32-msvc2017 -qt-zlib -qt-pcre -qt-libpng -qt-libjpeg -qt-freetype -opengl desktop -sql-odbc -sql-sqlite -make libs -nomake tools -nomake examples -nomake tests -openssl-linked OPENSSL_LIBS="-llibssl -llibcrypto" -I c:\openssl\build32\include -L c:\openssl\build32\lib
          

          If I run this same command (including prefix) from the qt-everywhere-src-5.12.0 (sources) folder, then build works perfectly fine.

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

            Qt 5.12.1 just got released. Could you check it the same thing still happens to you ?

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

            T 1 Reply Last reply
            0
            • SGaistS SGaist

              Qt 5.12.1 just got released. Could you check it the same thing still happens to you ?

              T Offline
              T Offline
              Taytoo
              wrote on last edited by
              #5

              @SGaist Same error.

              Noticed that at the end of the config (only on 15.12.1) I'm getting a message about ensuring LLVM path is setup properly. Never seen anywhere else that I need LLVM to build sources on Windows using VS. Is LLVM needed now?

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

                Yes it is, since 5.11, see the QDoc Dependencies.

                As for your problem, you should check the bug report system to see if there's already something there. You're not the only one to which it happens. If nothing is already available, please open a new report with the complete procedure you used to build Qt statically so it can be easily reproduced.

                [mrjj fixed qdoc link]

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

                1 Reply Last reply
                2
                • T Offline
                  T Offline
                  Taytoo
                  wrote on last edited by
                  #7

                  In case anyone runs into the same problem. The fix was prefix path, you have to append \qtbase to whatever path you choose for shadow build folder.

                  E.g. if you wanted shadow build in folder "c:\qt\static\5.12.1" then prefix would be "-prefix c:\qt\static\5.12.1\qtbase". The shadow build would still be in the "c:\qt\static\5.12.1" folder.

                  1 Reply Last reply
                  2

                  • Login

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