Someone mentioned the eyes widget on another mailing-list.
----- Original Message ---- From: Tico Ballagas <[email protected]> To: Jim Smith <[email protected]> Cc: [email protected] Sent: Wed, August 4, 2010 3:19:38 PM Subject: Re: [Qt-mobility-feedback] Troubles building against qt 4.7 I don't know of any examples outside of the Qt mobility to test. Do you know of any? None of the existing Qt mobility examples work. Thanks -Tico On Aug 4, 2010, at 10:08 AM, Jim Smith wrote: > I assumed there was no output at all. If you're not able to start the > Accelerometer it's possible that another process is using it. Are other > applications able to use it? > > > Jim > > > > > ----- Original Message ---- > From: Tico Ballagas <[email protected]> > To: Jim Smith <[email protected]> > Cc: [email protected] > Sent: Tue, August 3, 2010 10:37:59 AM > Subject: Re: [Qt-mobility-feedback] Troubles building against qt 4.7 > > I'm building using scratchbox. I've installed the qt4-experimental packages > in > > both scratchbox and on my N900. > > [sbox-FREMANTLE_ARMEL: ~/qt-mobility-1.0.2] > which qmake > /opt/qt4-maemo5/bin/qmake > [sbox-FREMANTLE_ARMEL: ~/qt-mobility-1.0.2] > ./configure -modules sensors > Configuring Qt Mobility > > Checking available Qt ... 4.7.0 > Checking QMF ... Not Found > Checking NetworkManager ... Not Found > Checking CoreWLAN (MacOS 10.6) ... Not Found > Checking Maemo ICD ... Not Found > Checking Maemo ICD WLAN ... OK > Checking Maemo5 contacts dependencies ... OK > Checking Bluez ... OK > Generating Mobility Headers... > > I didn't install any qt-mobility libraries because they depend on 4.6 and my > code depends on 4.7. > > After compilition (make install), the install /qt-mobility-1.0.2/install > directory has the following contents: > > ---------------------------------------- > > [sbox-FREMANTLE_ARMEL: ~/qt-mobility-1.0.2/install] > ls -R > .: > include lib plugins translations > > ./include: > QtSensors qmobilityglobal.h > > ./include/QtSensors: > QAccelerometer QProximityFilter QTapSensor > QAccelerometerFilter QProximityReading qaccelerometer.h > QAccelerometerReading QProximitySensor qambientlightsensor.h > QAmbientLightFilter QRotationFilter qcompass.h > QAmbientLightReading QRotationReading qmagnetometer.h > QAmbientLightSensor QRotationSensor qorientationsensor.h > QCompass QSensor qproximitysensor.h > QCompassFilter QSensorBackend qrotationsensor.h > QCompassReading QSensorBackendFactory qsensor.h > QMagnetometer QSensorFilter qsensorbackend.h > QMagnetometerFilter QSensorManager qsensormanager.h > QMagnetometerReading QSensorPluginInterface qsensorplugin.h > QOrientationFilter QSensorReading qtapsensor.h > QOrientationReading QTapFilter qtimestamp > QOrientationSensor QTapReading > > ./lib: > libQtSensors.prl libQtSensors.so.1 libQtSensors.so.1.0.2 > libQtSensors.so libQtSensors.so.1.0 > > ./plugins: > sensors > > ./plugins/sensors: > libqtsensors_generic.so libqtsensors_n900.so > > ./translations: > qtmobility_ar.qm qtmobility_fr.qm qtmobility_pt.qm qtmobility_uk.qm > qtmobility_cs.qm qtmobility_he.qm qtmobility_ru.qm qtmobility_zh_CN.qm > qtmobility_da.qm qtmobility_hu.qm qtmobility_sk.qm qtmobility_zh_TW.qm > qtmobility_de.qm qtmobility_ja_JP.qm qtmobility_sl.qm > qtmobility_es.qm qtmobility_pl.qm qtmobility_sv.qm > > -------------------------------- > > I copied these files to the n900 /opt/qt4-maemo5/ > > Nokia-N900:/home/user# ./accel > Accelerometer didn't start! > > Then I try to run accel and I get the error. Just as a sanity check, I ran > > Nokia-N900:/home/user# ldd accel > libQtSensors.so.1 => /opt/qt4-maemo5/lib/libQtSensors.so.1 (0x40001000) > libQtCore.so.4 => /opt/qt4-maemo5/lib/libQtCore.so.4 (0x40034000) > libpthread.so.0 => /lib/libpthread.so.0 (0x41168000) > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x41670000) > libm.so.6 => /lib/libm.so.6 (0x41320000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x41150000) > libc.so.6 => /lib/libc.so.6 (0x41028000) > libQtGui.so.4 => /opt/qt4-maemo5/lib/libQtGui.so.4 (0x4032d000) > libQtDBus.so.4 => /opt/qt4-maemo5/lib/libQtDBus.so.4 (0x40e43000) > libQtXml.so.4 => /opt/qt4-maemo5/lib/libQtXml.so.4 (0x40ee6000) > libz.so.1 => /usr/lib/libz.so.1 (0x413d0000) > libdl.so.2 => /lib/libdl.so.2 (0x412c8000) > libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x41460000) > librt.so.1 => /lib/librt.so.1 (0x41190000) > libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x411a8000) > /lib/ld-linux.so.3 (0x41000000) > libpng12.so.0 => /usr/lib/libpng12.so.0 (0x41800000) > libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x41758000) > libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x412d8000) > libEGL.so => /usr/lib/libEGL.so (0x40f3f000) > libSM.so.6 => /usr/lib/libSM.so.6 (0x44fe8000) > libICE.so.6 => /usr/lib/libICE.so.6 (0x44ee8000) > libXrender.so.1 => /usr/lib/libXrender.so.1 (0x41990000) > libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x417d0000) > libXext.so.6 => /usr/lib/libXext.so.6 (0x41840000) > libX11.so.6 => /usr/lib/libX11.so.6 (0x41528000) > libIMGegl.so => /usr/lib/libIMGegl.so (0x40f4b000) > libexpat.so.1 => /usr/lib/libexpat.so.1 (0x414b8000) > libXau.so.6 => /usr/lib/libXau.so.6 (0x41508000) > libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x41518000) > libsrv_um.so => /usr/lib/libsrv_um.so (0x40f60000) > > > > On Aug 3, 2010, at 2:57 AM, Jim Smith wrote: > >> Hi, >> >> It sounds like you're missing some required libs on the device. Make sure >> you > > >> have all of the dependencies needed by the executable on the device and in >> a >> location that's in the path. If you don't do this your executable will not >> start because it won't be able to find the libraries it's linked against. >> >> >> Did you install Qt 4.7 and Qt-Mobility-1.0.2 on the device? How did you do > it? >> >> >> Jim Smith >> [email protected] >> >> >> >> >> ----- Original Message ---- >> From: Tico Ballagas <[email protected]> >> To: Rohan McGovern <[email protected]> >> Cc: "[email protected]" <[email protected]> >> Sent: Tue, August 3, 2010 3:46:25 AM >> Subject: Re: [Qt-mobility-feedback] Troubles building against qt 4.7 >> >> Thanks for the clarification >> >> All I really want is the sensor library for now. I'm able to successfully >> build >> >> when I run: >> # ./configure -modules sensors >> # make >> # make install >> >> Then I copied the ./install directory to the device and installed them using >> # cp -r . /opt/qt4-maemo/ >> >> However, when I tried the accelerometer example, I got: >> # ./accel >> Accelerometer didn't start! >> >> Any ideas what might be going wrong here? How might I go about debugging >> what > > >> went wrong? >> >> Best >> -Tico >> >> On Aug 3, 2010, at 12:31 AM, Rohan McGovern wrote: >> >>> 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 >> >> >> >> >> > > > > _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
