qmake

I'm using QT 5.9.1 working on Mac OS. My project is mobile App with C++ logic and QML UI Layer. All QML files are included into qml.qrc file, so in my .pro file I have RESOURCES += qml.qrc Inside qml.qrc there is a list of all resource files I use in Project, such as pictures, icons and QML files, in QT Creator it's displayed OK: As you can see some QML files are located in ROOT path of qml.qrc when other files are in subfolders , e.g. "qrc:/Elements/". So problem is that whenether I make changes in Files that located in root of qml.qrc - they are normally recompiled when I press build,

Is there a way to use the .pro file in Qt to call another Makefile? For example, in a makefile, you could use: make -f /other/path/Makefile Is there anything like using the pro file for Qt? Something like this should work: QMAKE_EXTRA_TARGETS += other PRE_TARGETDEPS += other other.commands = make -f /other/path/Makefile this will cause make -f /other/path/Makefile to be called as part of the make process, and will also give you the ability to type make other to just run that command. 来源： https://stackoverflow.com/questions/10488458/qt-pro-file-call-another-makefile

In Qt Creator, I have a pro file using PRECOMPILED HEADERS. The build works just perfect when I build in Release mode. But building in Debug mode gives errors, generating object files failing. Example: 17:12:40: Running steps for project Euclide... 17:12:40: Configuration unchanged, skipping qmake step. 17:12:40: Starting: "C:\Qt\Tools\mingw48_32\bin\mingw32-make.exe" C:\Qt\5.2.0\mingw48_32\bin\qmake.exe -spec win32-g++ CONFIG+=debug -o Makefile ..\euclide\Euclide.pro C:/Qt/Tools/mingw48_32/bin/mingw32-make -f Makefile.Debug mingw32-make[1]: Entering directory 'C:/UserPrograms/Euclide/build' g

From Visual Studio 2008 Command Prompt I run this command to generate .vcproj file: >qmake -spec win32-msvc2008 And get a warning message: WARNING: Generator: MSVC.NET: Found more than one version of Visual Studio in your path! Fallback to lowest version (MSVC.NET 2008 (9.0), MSVC.NET 2008 Express Edition (9.0), MSVC.NET 2005 (8.0), MSVC.NET 2008 (9.0) in path, MSVC.NET 2008 Express Edition (9.0) in path) For this project I use MSVS 2008 Professional. Actually the generated .vcproj file works well, but what is the warning message about? I removed all references of the older version of Visual

I am trying to create a DLL that will call Qt (currently I can't use Jambi for the functionality I need). I have a simple Java method: public final native int createChild(int handle); I created C project in Visual Studio Express 2010 and was able to build the DLL. Then I created a project in Qt creator and moved my sources there. I tried to configure the build to a best of my knowledge but all I get is: java.lang.UnsatisfiedLinkError: tools.proofofconcept.control.EmbedderComposite.createChild(I)I My guess is that symbol is not properly exported from DLL. I added -D_JNI_IMPLEMENTATION_ linker

While reading through the documentation for Qt 5.1, and specifically qmake, I was stumped by the explanation given in the documentation for the qmake CONFIG() function. I completely understood the one-argument version of the function, but the two-argument version makes absolutely no sense to me. I think my confusion is coming from the lack of a definition for 'active config' since the Qt 5.1 documentation says the following: This function can be used to test for variables placed into the CONFIG variable. This is the same as scopes, but has the added advantage that a second parameter can be

I'm trying to open an xml file in the current location of the executable QString path = QDir::currentPath(); path.append("/acc.xml"); QFile file(path); if(!file.open(QIODevice::ReadOnly)) { insertItem("IO ERR"); } When I run it from Qt creator, everything works. currentPath() returns the path to the executable's folder When I go to project-build-desktop/ folder and try to run it manually currentPath() returns /home/user/Documents EDIT also tried with same results: Qt::current().path(); Qt::current().absolutePath(); Johnny Try to use QCoreApplication::applicationDirPath() instead of QDir: