Hi Daniel,

>Then I tried MacOSX10.6.sdk
>./configure -sdk /Developer/SDKs/MacOSX10.6.sdk (OK)
>make
>ERROR with the following message:

>Undefined symbols:
>"QtMobility::QLandmarkFileHandlerGpx::setWaypoints(QList<QtMobility::QLandmark>
>const&)", referenced from:
>exportLandmarksGpx(QString const&, QIODevice*,
>QList<QtMobility::QLandmarkId>, QtMobility::QLandmarkManager::Error*,
>QString*, QString const&)in qlandmarkmanagerengine_sqlite.o
>"QtMobility::QLandmarkFileHandlerLmx::exportData(QIODevice*, QString
>const&)", referenced from:
>exportLandmarksLmx(QString const&, QIODevice*,
>QList<QtMobility::QLandmarkId>, QtMobility::QLandmarkManager::Error*,
>QString*, QString const&)in qlandmarkmanagerengine_sqlite.o
>"QtMobility::QLandmarkFileHandlerGpx::importData(QIODevice*)",
>referenced from:
>importLandmarksGpx(QString const&, QIODevice*,
>QtMobility::QLandmarkManager::Error*, QString*, QString const&,
>QueryRun*)in qlandmarkmanagerengine_sqlite.o
>.
>exportLandmarksLmx(QString const&, QIODevice*,
>QList<QtMobility::QLandmarkId>, QtMobility::QLandmarkManager::Error*,
>QString*, QString const&)in qlandmarkmanagerengine_sqlite.o
>exportLandmarksLmx(QString const&, QIODevice*,
>QList<QtMobility::QLandmarkId>, QtMobility::QLandmarkManager::Error*,
>QString*, QString const&)in qlandmarkmanagerengine_sqlite.o
>"QtMobility::QLandmarkFileHandlerGpx::exportData(QIODevice*, QString
>const&)", referenced from:
>exportLandmarksGpx(QString const&, QIODevice*,
>QList<QtMobility::QLandmarkId>, QtMobility::QLandmarkManager::Error*,
>QString*, QString const&)in qlandmarkmanagerengine_sqlite.o
>ld: symbol(s) not found
>collect2: ld returned 1 exit status
>make[4]: *** [libqtlandmarks_sqlite_debug.dylib] Error 1
>make[3]: *** [debug-all] Error 2
>make[2]: *** [sub-sqlite-make_default-ordered] Error 2
>make[1]: *** [sub-landmarks-make_default] Error 2
>make: *** [sub-plugins-make_default-ordered] Error 2

For the landmark errors at least, you can work around those by using the -tests 
option in your configure line.
On qt labs there was a comment by Alex at 6:20am, July 28, 2010 that explains 
this a bit more:
http://labs.qt.nokia.com/2010/07/27/qt-mobility-110-technology-preview/

An alternative is to not build the location module if you're not interested in 
using that.  You can use the -modules option in the configure line
eg configure -modules "messaging" to only build the messaging library.

Regards,
Amos





_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback

Reply via email to