Tico Ballagas said: > I get the following compiler errors when trying to build against Qt 4.7: > > compiling qmessagecontentcontainer.cpp > /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtCore/qdatastream.h: In > function 'QDataStream& operator>>(QDataStream&, QList<T>&) [with T = > QString]': > /usr/include/QtCore/qstringlist.h:247: instantiated from here > /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtCore/qdatastream.h:246: > error: 'class QList<QString>' has no member named 'reserve' > make[3]: *** [../../build/Debug/QtMessaging/qmessagecontentcontainer.o] Error > 1 > make[3]: Leaving directory `/home/ballagas/qt-mobility-1.0.2/src/messaging' > make[2]: *** [sub-messaging-make_default] Error 2 > make[2]: Leaving directory `/home/ballagas/qt-mobility-1.0.2/src' > make[1]: *** [sub-src-make_default-ordered] Error 2 > make[1]: Leaving directory `/home/ballagas/qt-mobility-1.0.2' > make: *** [debian/stamp-makefile-build] Error 2 > > Has anyone been successful at building against qt 4.7?
It's a bit complicated. The problem is that you're mixing two sets of Qt headers, one in /usr/include and one in /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/ . Fixing that is not so easy, because Mobility depends on some packages which depend on Qt, and those packages were built against Qt in /usr. That means pkg-config tells the build system to put /usr/include/QtCore etc into the include path even when you're building against Qt in /opt/qt4-maemo5. (That's just one problem, there are others...) AFAIK you can fix it by doing one of these: - Instead of building Qt 4.7 into /opt/qt4-maemo5, build it into /usr. But if you do this on a real device then you might break some important things. - Build Qt 4.7 into /opt/qt4-maemo5; identify all of the dependencies of Mobility which use Qt; rebuild them all against Qt in /opt/qt4-maemo5 (and install them to /opt/qt4-maemo5 too). > Also how would you build experimental debian packages that install to the > /opt/qt4-maemo/ directories on the device? Some Nokia guys are working on experimental mobility packages which go under /opt/qt4-maemo5 but it's not ready yet. For the reasons above, it's not just a quick "change one configure option" kind of thing. -- Rohan McGovern QA Engineer Qt Development Frameworks, Nokia _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
