qmake

What is the difference between *.pro and *.pri configuration files for qmake? What should go into a *.pro file and what should go into a *.pri file? A .pro file is what you would run QMake on. A .pri file is included by a .pro file. Other than that there is not much of a difference between the two. Example usage could be if you have different builds which need different options. You could put shared information in the .pro, while deferring the options to various .pri files. A bit more information, although admittedly not much more, can be found here . lpapp There is one main difference between

I have a qmake file generated by Qt creator. I am modifying it but I do not manage to understand how to create a variable. For example, I want to declare the library MYPATH as I did here: MYPATH = /lib/aaa/bbb unix:!macx:!symbian: LIBS += -L$(MYPATH) When I run qmake I find in the generated makefile LIBS = ....... -L$(MYPATH) ..... But the MYPATH variable is not declared anywhere. Does anyone know how to declare such a variable properly? jwernerny QMake uses its own syntax for variable references . VAR = foobar => Assign value to variable when qmake is run $$VAR => QMake variable's value at

I'm currently using C++11 features in my Qt applications. However, I'd like to use some of the new C++14 features in my applications. To enable C++11 in a Qt application, one only needs to add one line in the qmake project file, namely: CONFIG += c++11 or this for earlier versions: QMAKE_CXXFLAGS += -std=c++1y I already tried to do the same with C++14, but it didn't work. I changed the above mentioned line of the qmake project like this: CONFIG += c++14 or this for earlier versions: QMAKE_CXXFLAGS += -std=c++1y After that, lots of compilation errors, that did not exist before, appear when

What changes must I make to the .pro file if I want to execute chmod command, execute the output binary file, or do some other operations. Dariusz Scharsig 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 QMAKE_EXTRA_TARGETS += mytarget This way, you have an extra target

There are several questions on SO regarding how to create a pre-build step for qmake , I can do that with this in my .pro file: versionTarget.target = ../VersionData/versioning.h versionTarget.depends = FORCE win32: versionTarget.commands = cd $$PWD; python.exe ./version_getter.py -p $$TARGET else: versionTarget.commands = cd $$PWD; python ./version_getter.py -p $$TARGET PRE_TARGETDEPS += ../VersionData/versioning.h QMAKE_EXTRA_TARGETS += versionTarget Now, the problem is that this approach is not a build step per se but just another build target, so if I have the -j flag configured for make