Qmake on Mac is missing for qt-creator

Question

I am currently working on Mac OS X and want to start building applications using Qt Creator . Unfortunately, I cannot create any applications, as this gives me an error saying that the qmake path was not found or qmake is missing.

I tried using netbeans, which works fine with simple c / C ++ programs, but for qt applications it gives me the same error. My version of Xcode 4 works fine and builds without problems.

Any ideas?

Thanks:)

Answer 1

It’s not enough just to download Qt Creator , you need to download the full sdk file: http://qt.nokia.com/downloads (almost 1GiB)

Answer 2

My Macbook is no longer my primary computer. But, when it was, I found out from painful sensations that it is best to install software from MacPorts, whenever you want, from http://www.macports.org/

More importantly, I also found that when the software was not offered by MacPorts, it was unchanged because that particular software could not be installed without any configuration on the Mac. Therefore, since Macports does not currently offer Qt v5, and I had problems installing the qt -project.com Qt v5.2.1 SDK on my Macbook, I would recommend going with MacPort for Qt v4.8.5 [qt4-mac], which includes qmake. Qt Creator is available as a standalone MacPort [qt4-creator-mac].

Here's how I successfully installed Qt v4.8.5 [with qmake] and Qt Creator on my Macbook:

1) 'sudo port install qt4-mac'

2) 'sudo port install qt4-creator-mac'

3) I used Finder to run Qt Creator, which was in the / Applications / MacPorts / Qt 4 folder.

4) When I first started Qt Creator, an automatically installed desktop set was specified in the Settings dialog box, but this set did not have a Qt version, no qmake and no debugger.

5) Manually added a second set.

6) A configured Qt version kit for / opt / local / bin / qmake, where qt4-mac has qmake installed. This was enough for the kit to now detect Qt v4.8.5, which was installed by qt4-mac.

7) The function of automatic detection of the kit used to detect the debugger.

8) Configure this kit as the default kit.