On Wednesday, 2 de November de 2011 10:03:12 Rohan McGovern wrote: > In other words, if you test contains(QT_CONFIG,some_module) in your Qt5 > module, you've made your build behavior implicitly depend on the order in > which the user happened to run `qmake' over the qt5 modules, which is > largely undefined. e.g. if you are doing a `make -j20' in qt5.git, the > qmakes are also parallelized, and your result might flipflop between > builds.
Tell me about it...
Turns out that all my woes trying to build a brand-new Qt were caused by a
make -j6 in the top-level qt5.git repository, made worse by using a script
that runs make --dry-run first (dry-run doesn't run, but it *does* make
Makefiles, which runs qmake for real).
So instead of using the Makefile from there, I have my own script now to build
all of Qt.
PS: are the unit tests outside qtbase ever compiled? The qtxmlpatterns ones
don't build for me.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
