Hi Eero, It is great to hear from you Nokia guys - I thought I would never get a reply. But thanks for responding - Finland seems to be back on track :-)
Alright, I am now using the mobility feedback list, as you suggest. Regarding the issue, “From what I can gather it seems that mobility.prf is not properly deployed Does this deployment of mobility.prf require developer intervention? If yes, where are the notes/instructions? If not, its not my problem. There should not be the need to manually declare the LIBS in project files Would need a VIDEO proof to believe this :-) Can bet my treasure for this. (Fyi, I am using Windows) I NEED to do it every time before I build for the device, its painful but I have got used to it by using ctrl+z and ctrl+y in the pro file when I need to switch the build targets. Maybe different Qt versions are used Nokia Qt SDK is what I have installed after seeing Lucian Tomuta's video about Qt development. The video is nice for Symbian devices. For Maemo devices there is also a video - but not that great. Picachu On Wed, Aug 18, 2010 at 11:36 AM, <[email protected]> wrote: > Hi, > > > > I got following answer from one of the QtMobility developers: > > > > “From what I can gather it seems that mobility.prf is not properly > deployed. There should not be the need to manually declare the LIBS in > project files. That's one of the purposes of the MOBILITY+=.. and > CONFIG+=mobility lines in the project file. The missing header is a similar > indicator too. > > > > The mystery is why it works in emulator builds but not device builds. Maybe > different Qt versions are used?” > > > > In future, please use > lists.trolltech.com/mailman/listinfo/qt-mobility-feedback for mobility > related issues. > > > > Cheers, > > > > Eero > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *ext Picachu Nioto > *Sent:* 16 August, 2010 13:05 > *To:* [email protected] > *Subject:* [QtS60-feedback] QtMobility Issues > > > > Hello friends from Qt Mobility, > > > > I have started using Qt Mobility with some conviction after reading some > bad reviews of it. > > > > But I am facing some problems, and I didn't find answers anywhere that > worked for me. So I am posting here :-) > > > > 1. I used messaging from Mobility APIs in my code. I tried on the emulator > and works fine. > > > > *"#include <QMessage>* > > *#include <qmessageservice.h>"* > > > > > > and in pro file > > > > *CONFIG += mobility* > > *MOBILITY += messaging * > > > > > > > > is what I included in my code for messaging. Now when I build for the device, > I had to put the following in the pro file to get a sis file created, which > worked well. > > > > > > *LIBS += -lQtMessaging \* > > * -lQtContacts \* > > > > * -lQtNetwork \* > > > > * -lsqlite3 \* > > > > * -L/usr/lib \* > > > > * -L/lib* > > > > > > Now the emulator doesn't build with the above LIBS in the pro file. This is > my issue #1. What is the solution for seamless building of the emulator and > device builds? > > > > > > 2. Now I added some code using contacts API. > > > > > > *#include "qtcontacts.h"* > > > > > > is what I use in code and also added > > > > > > > > *MOBILITY += messaging contacts* > > > > > > > > in my pro file. > > > > > > > > The emulator builds works, but I cannot add or remove contacts, etc. The > functions for contacts and softkeys don't work, so I need to test in on a > device. > > > > > > When I build for the device, it gives me error that qtcontacts.h is not > found. (even after using the LIBS above) > > > > > > So what is the solution that the Qt Mobility team or manager suggest? and is > it published anywhere online? If no why not? > > > > > > Thank you Mobility team if you answer. > > > > > > Picachu > > > >
_______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
