switch to CMake for the superproject as you mentioned or.
Most convenient is to unify on the build system. when the subproject needs to be fully built before qmake can be run for the superproject or when you want to open the project as a whole under Qt Creator (subproject’s files would not be listed in project tree). In specific cases, it is possible to use qmake’s $$system() function and QMAKE_EXTRA_TARGETS variable to invoke cmake/make on a subproject. The source, using the primitive subdirs approach is here (only a skeleton thus far): I’m probably thinking in the wrong direction. My preference would be to use separate build steps, be able to include submodules from other projects via git that use cmake, but stick to ‘straight’ qmake for the sailfish apps. What should I do, attempt to come up with a recipe for mixing build steps (must be doable)? Switch everything as some Sailfish devs have done to cmake? On the other hand, the future of QT (sometime in the evolution of 6) is pointing at cmake anyway. But I’d prefer to use qmake (someone will probably hate me for saying that I just find qmake in the Sailfish SDK context to be clean to work with managing with. So, I want to use a library which the author supplies with cmake build files. For the example I’m working on, where the entire library could actually be put in a single file and header, that’s ok. This is great if you controll all the code.
Simplesynth setup how to#
I’ve just gotten great advice in a sailfish context for how to use the subdirs templates for dependancy building.
0 kommentar(er)
