Alan Alpert said: > On Thu, 20 Oct 2011 19:10:34 ext Thiago Macieira wrote: > > On Thursday, 20 de October de 2011 10:04:29 Rohan McGovern wrote: > > > The compilation procedure only includes the things which are compiled by > > > default, though (e.g. if a module does not appear in qt.pro then it is > > > not included in this test). > > > > Does that include the unit tests? > > > > /home/thiago/src/qt/qt5/qtdeclarative/tests/auto/declarative/qdeclarativeco > > mponent/tst_qdeclarativecomponent.cpp:117:59: error: ‘QTRY_VERIFY’ was not > > declared in this scope > > > > QTRY_VERIFY is declared in qtbase/tests/auto/shared/util.h and that header > > is not visible outside qtbase. > > That's just a qtbase version mismatch, > ae1810658b75dd0eb0247b0e951ce315c8ce4c86 in qtbase moves QTRY_VERIFY into > qtestcase.h >
Yes, and to reiterate: the qt5.git submodules are kept pointing to a combination of SHA1s which have been successfully compiled. In qt5.git, qtbase would not be updated to include ae1810658b75dd0eb0247b0e951ce315c8ce4c86 until/unless qtdeclarative received a commit to unbreak compile. _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
