On 20/12/12 22:53, andy fillebrown wrote: > Whelp, all the examples and tests are being built. Bummer. I'm > thinking now that it might be because I used the -r flag for the call > to qmake.
The -r means "go into subdirectories and build their Makefiles too" but it finds subdirectories using SUBDIRS entries, not by scanning the filesystem. The primary advantage to running qmake with -r is that it makes all the Makefiles up-front and it guarantees that the Makefiles are built with the config you specified. If you don't use -r and there are Makefiles in the tree they may not get re-built based on the config you specified. The .config=no_default_make (something like that anyway) is what stops "make" from descending into that directory (there's another one for make install). Naturally, this was removed from all the .pro files near the end of 5.x development so you can't even tell what's going on anymore (you now have to look into .prf files somewhere). Normally, the option to disable examples and tests is preserved in build-wide config. As a common pattern, I would build Qt without examples or tests and then build one module with examples and tests by running: qmake -r QT_BUILD_PARTS+=examples QT_BUILD_PARTS+=tests qtsensors.pro But this was on Linux and a few months ago... -- Link _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest