After quite a bit of frustration with qmake, I have found what I think is the answer to your question. If not, then I have learned the way that I will use qmake until I find something better, because this is still a little bit ugly. I set up a demo project, this is my … Read more
In the article you linked to, it’s said in the very beginning that the project file is processed three times. This should answer your first question; since it’s processed three times, your message() is executed three times too. Why is it processed multiple times? Because qmake does not build your project! It only generates build … Read more
You can use a qmake function for reusability: # Copies the given files to the destination directory defineTest(copyToDestdir) { files = $$1 for(FILE, files) { DDIR = $$DESTDIR # Replace slashes in paths with backslashes for Windows win32:FILE ~= s,/,\\,g win32:DDIR ~= s,/,\\,g QMAKE_POST_LINK += $$QMAKE_COPY $$quote($$FILE) $$quote($$DDIR) $$escape_expand(\\n\\t) } export(QMAKE_POST_LINK) } then use it … Read more
I got the same error once , maybe source of your problem is different but I will write anyways. In my *.pro file, it was like : SOURCES += main.cpp\ mainwindow.cpp\ serialHelper.cpp \ serialHelper.cpp HEADERS += mainwindow.h\ += serialHelper.h \ serialHelper.h \ typeDefinitions.h cpp and header file was repeating itself. I delete the repeating includes … Read more
When using Qt Creator: Build → Run qmake Build → Rebuild All
Qt uses qmake to transparently support Qt’s various addons, including “moc, the meta-object compiler” (which provides signals & slots), “uic, the ui compiler” (which creates header files from .ui designer files), “rcc, the resource compiler” (which compiles resources). There’s nothing to stop you using any build system you want. however, it’s a lot more work. … Read more
You can add the following to the Qt .pro for C++11: – CONFIG += c++11 As of Qt 5.4, C++14 can be enabled with CONFIG += c++14
You are lacking the installation of the the QtSvg library. Try to install them on your Ubuntu 13.10 in the following way: sudo apt-get install libqt5svg5*
QMake uses its own syntax for variable references. VAR = foobar => Assign value to variable when qmake is run $$VAR => QMake variable’s value at the time qmake is run $${VAR} => QMake variable’s value at the time qmake is run (identical but enclosed to separate from surrounding text) $(VAR) => Contents of an … Read more
DEFINES += “WINVER=0x0500” works for me. This way, -DWINVER=0x0500 is added to the command line of the compiler, which is the syntax GCC/mingw expects for command line preprocessor definitions (see here for the details).