we would like to install different builds on the same machine and the place were would do that distinction would be on the .pro file, to then generate different values for the "version" value of "info.plist" file.
We already have a portion of code that we can probably use to do something similar:
Hi @daljit97, as you guessed, the difficulty is in helping Qt to find the appropriate metadata so that qmake knows how to handle "KSyntaxHighlighting" when it finds it in your QMake project file.
Looking at some of the Qt docs on a related topic, I found this page on advanced QMake usage.
The part you care about is the third option to add features to qmake: using the QMAKEPATH environment variable. By exporting this variable in your shell to the KF5 install directory, qmake should be able to find the various KF5 modules.
For example, my KF5 install is at ~/kde-5, so I did something like:
It is also possible to build Qt applications with CMake, and that is more traditional for significant KF5 users. But as long as this works for you it looks like it won't be too hard to do what you're trying to do while continuing to use qmake.
Ok so that was very helpful. On my machine that KSyntaxHighlighting had a .pri file in /usr/lib/x86_64-linux-gnu/qt5/mkspecs/modules. Following your suggestion I added a QMAKEPATH Environment variable in Qt Creator using the GUI tool that Qt Creator provides and now everything works!
I have the same message error with a new created project (QtCreator v4.9.2)
("...exited with code -1 \n The process failed to start. Either the invoked program ... is missing, or you may have insufficient permissions to invoke the program.")
I compared the run config with my others olders projects, and finaly I unchecked the "run in terminal".
Now, I'm able to run my project with QtCreator.
Hi Patrick. I'm in the same situation. Installation on archlinux using the official qt5.13 online installer. Android and desktop kits are well configured on qtcreator just by using their respectif qmake. However when I choose the one.of webassembly (wasm_32) distributed by qt, qtcreator warns about the ABI, saying that it is not defined. Its value is unknown-unknown-unknown-.....
I compiled a simple qt project using wasm_32 kit but link fails with the following error main.o: architecture machine must be wasm32.
@SoheilSabz If you're creating a plug-in for designer then you need to copy the final plug-in library to the same location where other designer plug--ins are. Also, you have to use same Qt version which was used to build your version of designer.