Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Building from source in release mode - no qmake.exe or mkspecs installed
Forum Update on Monday, May 27th 2025

Building from source in release mode - no qmake.exe or mkspecs installed

Scheduled Pinned Locked Moved Unsolved General and Desktop
qt5.9.2windows
8 Posts 3 Posters 3.9k 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.
  • G Offline
    G Offline
    grahamm
    wrote on last edited by A Former User
    #1

    Hello all,

    I've just downloaded, built, and installed Qt 5.9.2 in Windows. The steps were "configure <args>", "jom -j4", and "jom install". I've tried both debug and release builds ("-debug" and "-release" args to configure). My application uses CMake to build it. With the debug build of my application, everything works correctly. But with the release build, CMake can't find qmake.exe. When I look in the installed Qt directory in the bin sub-directory, there is no qmake.exe. In the debug installation, that file is there. I manually copied it from the Qt build directory to the installed directory and then CMake failed on mkspecs/win32-msvc. I copied that too and now things appear to be working. I did not have the problem with Qt 5.9.1.

    Can somebody please confirm that this is the case, or did I do something wrong?

    Thanks for any help,
    Graham

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

      Hi,

      If you would like somebody to confirm, you should at least give the exact parameters you used to build your version of Qt and if you used out of source builds.

      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
      • G Offline
        G Offline
        grahamm
        wrote on last edited by
        #3

        Thanks for replying. For the debug build, my configure command is:

        configure -prefix c:\Qt\5.9.2_msvc2017_debug -opensource -confirm-license -debug -platform win32-msvc -I c:\pgsql\include -L c:\pgsql\lib -nomake examples -nomake tests -sql-psql -make-tool jom

        for release, it's:

        configure -prefix c:\Qt\5.9.2_msvc2017_release -opensource -confirm-license -release -platform win32-msvc -I c:\pgsql\include -L c:\pgsql\lib -nomake examples -nomake tests -sql-psql -make-tool jom

        Thanks,
        Graham

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

          Did you do these two builds out of source builds ? If not, did you clean the sources before calling configure again ?

          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
          • G Offline
            G Offline
            grahamm
            wrote on last edited by
            #5

            Thanks for replying again.

            I did the two builds in separate source directories, so no need to clean between them. I'm not sure what you mean by "out of source builds" (but I presume that doing them in separate directories makes this irrelevant).

            By the way, the problem does not happen on Linux builds.

            Graham

            jsulmJ 1 Reply Last reply
            0
            • G grahamm

              Thanks for replying again.

              I did the two builds in separate source directories, so no need to clean between them. I'm not sure what you mean by "out of source builds" (but I presume that doing them in separate directories makes this irrelevant).

              By the way, the problem does not happen on Linux builds.

              Graham

              jsulmJ Offline
              jsulmJ Offline
              jsulm
              Lifetime Qt Champion
              wrote on last edited by
              #6

              @grahamm Out of source build (lets say you have Qt source in c:\QtSource):

              mkdir c:\qt_build
              cd c:\qt_build
              ..\QtSource\configure.exe ...
              nmake.exe
              

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

              1 Reply Last reply
              1
              • G Offline
                G Offline
                grahamm
                wrote on last edited by
                #7

                Ok, gotcha.

                Thanks, jsulm.

                1 Reply Last reply
                0
                • G Offline
                  G Offline
                  grahamm
                  wrote on last edited by
                  #8

                  Nobody has replied, so I've entered it as a bug: https://bugreports.qt.io/browse/QTBUG-63901. I'll see what happens.

                  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