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. Qmake cannot find mkspec even though it is there
Forum Updated to NodeBB v4.3 + New Features

Qmake cannot find mkspec even though it is there

Scheduled Pinned Locked Moved Installation and Deployment
8 Posts 2 Posters 4.3k 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.
  • G Offline
    G Offline
    ggwolf
    wrote on last edited by
    #1

    Using Qt 5.2.1 on the mac, executing quake on my .pro file without any other args works fine. when I switch to another machine with the same setup, I get this trying to execute quake on my pro file. The directories are all the same and the macx-clang directory is there under /usr/local/Qt5.2.1/5.2.1/clang_64/mkspecs/macx-clang on both machines.

    /usr/local/Qt5.2.1/5.2.1/clang_64/bin/qmake EM.pro

    Could not find qmake configuration file macx-clang.
    Error processing project file: EM.pro

    I have tried specifying with the -spec argument but nothing helps. Should I just try reinstalling Qt 5.2.1 on the failing machine or what is the process to get it working?

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

      Hi,

      What does

      @qmake -query@

      return on your failing machine ?

      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
        ggwolf
        wrote on last edited by
        #3

        QT_SYSROOT:
        QT_INSTALL_PREFIX:/Users/mwolf/Qt5.2.1/5.2.1/clang_64
        QT_INSTALL_ARCHDATA:/Users/mwolf/Qt5.2.1/5.2.1/clang_64
        QT_INSTALL_DATA:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/
        QT_INSTALL_DOCS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/doc
        QT_INSTALL_HEADERS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/include
        QT_INSTALL_LIBS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/lib
        QT_INSTALL_LIBEXECS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/libexec
        QT_INSTALL_BINS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/bin
        QT_INSTALL_TESTS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/tests
        QT_INSTALL_PLUGINS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/plugins
        QT_INSTALL_IMPORTS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/imports
        QT_INSTALL_QML:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/qml
        QT_INSTALL_TRANSLATIONS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/translations
        QT_INSTALL_CONFIGURATION:/Library/Preferences/Qt
        QT_INSTALL_EXAMPLES:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/examples
        QT_INSTALL_DEMOS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/examples
        QT_HOST_PREFIX:/Users/mwolf/Qt5.2.1/5.2.1/clang_64
        QT_HOST_DATA:/Users/mwolf/Qt5.2.1/5.2.1/clang_64
        QT_HOST_BINS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/bin
        QT_HOST_LIBS:/Users/mwolf/Qt5.2.1/5.2.1/clang_64/lib
        QMAKE_SPEC:macx-clang
        QMAKE_XSPEC:macx-clang
        QMAKE_VERSION:3.0
        QT_VERSION:5.2.1

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

          Something strange here. You were writing about a Qt version installed in /usr/local however the one you are using seems to be in /Users/mwolf/

          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
            ggwolf
            wrote on last edited by
            #5

            Correct. the Qt directories in /Users/mwolf no longer exist. how would I modify these paths to point to /usr/local instead of my home?

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

              Did you simply move your Qt installation from your home folder to /usr/local ?

              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
                ggwolf
                wrote on last edited by
                #7

                I'm not sure, this machine is a build server that recently became my responsibility. I installed Qt on it before under my user. it seems the installation was moved like that. Should i do a

                @qmake -set@

                on all the values that need to be changed?

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

                  That won't be enough since your frameworks are probably also configured to look in the original path for dependencies. The most clean, fast and safe would be to re-install Qt properly

                  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

                  • Login

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