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. [Solved] QMAKESPEC has not been set ... Linux
Forum Updated to NodeBB v4.3 + New Features

[Solved] QMAKESPEC has not been set ... Linux

Scheduled Pinned Locked Moved Installation and Deployment
8 Posts 2 Posters 6.8k 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.
  • M Offline
    M Offline
    McLion
    wrote on 18 Sept 2014, 12:29 last edited by
    #1

    Hi

    I have cloned a Debian VM in which I perfectly can develop and compile my eLinux project.
    In the clone I created a new user account and set up everything for this new user.
    However, building the exact same project with the exact same sources returns:
    @QMAKESPEC has not been set, so configuration cannot be deduced.
    Error processing project file: src/qtgui.pro
    @

    I have echoed all parameters that are in the makefile and they are exactly the same as in the original VM. I have also compared the env to no avail. Does somebody have a clue how I get this thing to build?

    Thanks
    McL

    1 Reply Last reply
    0
    • A Offline
      A Offline
      andreyc
      wrote on 18 Sept 2014, 15:49 last edited by
      #2

      Did you install Qt from qt-project.org or it is Qt that comes with Debian?

      What is result of qmake -query ?

      1 Reply Last reply
      0
      • M Offline
        M Offline
        McLion
        wrote on 18 Sept 2014, 15:59 last edited by
        #3

        Thanks.
        Neither one. It's a package supplied from a chip manufacturer incorporating changes he made to have it work with his SDK to develop for his SoC.

        However, the query seems to help. It looks as if all the props point to the old user account (path in home directory) that has been used before cloning the VM instead of pointing to the current users respective path.

        How can I easily correct this, i.e. regenerating these props?

        1 Reply Last reply
        0
        • A Offline
          A Offline
          andreyc
          wrote on 18 Sept 2014, 16:07 last edited by
          #4

          Two options.

          Reinstall SDK under new user.

          Create a qt.conf file in SDK bin directory. The directory where is qmake and all other Qt tools are located

          Here is an example of qt.conf
          @
          [Paths]
          Prefix = /path/to/root/of/qt-sdk
          @

          Then run qmake -query to see a result.

          1 Reply Last reply
          0
          • M Offline
            M Offline
            McLion
            wrote on 19 Sept 2014, 07:53 last edited by
            #5

            Basically, this works. However, it does not set all built-in props as supposed.
            Where are these built-in props stored?

            1 Reply Last reply
            0
            • M Offline
              M Offline
              McLion
              wrote on 19 Sept 2014, 08:18 last edited by
              #6

              I did set all properties to the new user path using a shell script.
              Now, I have all properties doubled, with the old path as well as with the new path. How could the same property be there twice? Shouldn't that be overwritten?

              1 Reply Last reply
              0
              • M Offline
                M Offline
                McLion
                wrote on 19 Sept 2014, 09:27 last edited by
                #7

                As a matter of fact, compiling only works with your solution. I had to remove the QMake.conf that was created by QMake when I executed my script.
                It really looks as if the current props have been hardcoded into qmake at install/buildtime of the Qt package.

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  McLion
                  wrote on 22 Sept 2014, 14:14 last edited by
                  #8

                  The solution with the qt.conf works and I implemented a "svn-fit" solution that works for all users with a single touch at first co.
                  All tools in /bin have hardcoded paths.
                  I actually absolutely don't understand why one would design a system that creates executables with hardcoded paths in the firstplace ... but that's not the point here.

                  @ [Paths]
                  Prefix = /home/username/path/to/qt
                  Examples = examples
                  Demos = demos

                  @

                  1 Reply Last reply
                  0

                  1/8

                  18 Sept 2014, 12:29

                  • Login

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