I had a similar problem. I wanted a special tool (versioner) to run over the code every time the Makefile was executed. Here’s the solution: (to be read in the Qmake Manual, Configuring qmake’s Environment, Section: Customizing Makefile Output) Create you own Makefile target. Specify the command etc. mytarget.target = .buildfile mytarget.commands = touch $$mytarget.target … Read more
It looks like QMAKE_POST_LINK works well for this sort of thing. This seems to get the job done. my_batch_file.bat runs when nmake runs (rather than when qmake runs) and I don’t need to do anything funny with placeholder targets or files. It’s quite likely that I don’t need all of the items listed in ‘CONFIG’. … Read more
QMake: The required libraries. QT += core QT -= gui QT += network CMake: only the add is necessary. An exclude (QT -= gui) is not required. find_package(Qt5Core REQUIRED) find_package(Qt5Network REQUIRED) QMake: Additional Compiler flags: CONFIG += c++11 CMake: Extend the list of compiler flags as required. set(CMAKE_CXX_FLAGS “${CMAKE_CXX_FLAGS} -std=c++0x”) QMake: The source files SOURCES … Read more
I had a similar problem and I solved it by adding the following directive in the .pro file: QMAKE_CXXFLAGS_RELEASE -= -g Observe the _RELEASE suffix, otherwise don’t work.
This is now supported properly from Qt 5.4. You just type this into your qmake project file: CONFIG += c++14 The necessary code change went in the middle of 2014 by Thiago: Add support for CONFIG += c++14 I have just created the necessary documentation change: Mention the c++14 CONFIG option in the qmake variable … Read more
So I devised a rather creative solution to my problem… it appears that CMake has no functionality to detect the target architecture whatsoever. Now, we know we can easily do this in C because symbols like __i386__, __x86_64__, etc., will be defined depending on your environment. Fortunately CMake has a try_run function which will compile … 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
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).
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
Another option would be to start with the project file snippet in your original question, and also ensure that qmake is aware that versioning.h is a dependency for the other build targets in your project file — Add the full path to versioning.h to your HEADERS variable. Add the folder in which versioning.h resides to … Read more