View Single Post
Posts: 112 | Thanked: 122 times | Joined on Dec 2009 @ London, United Kingdom
#50
Hey there,

Having a bit of a problem to use qtm-12-connectivity (Bluetooth). Build will find the CamelCase headers (e.g. QBluetoothUuid ) but not the actual headers pointed by those (qbluetoothuuid.h).

I'm using QtSdk, so I installed qtm-12-* using
Code:
Maemo/4.6.2/bin/mad-admin xdpkg -i <<all pkgs>>
Code:
#:~/QtSDK/Maemo/4.6.2/bin$ ./mad-admin xdpkg -l
 libqtm-12-bearer 
 libqtm-12-connectivity 
 libqtm-12-contacts 
 libqtm-12-declarative 
 libqtm-12-dev 
 libqtm-12-feedback 
 libqtm-12-gallery 
 libqtm-12-location 
 libqtm-12-messaging 
 libqtm-12-multimedia 
 libqtm-12-organizer 
 libqtm-12-publishsubscribe 
 libqtm-12-sensors 
 libqtm-12-serviceframework 
 libqtm-12-systeminfo 
 libqtm-12-versit
And added CONFIG += mobilit12 and MOBILITY += connectivity to the .pro file.

I'm suspecting that somehow my installation misses those headers.
Code:
#:~/QtSDK/Maemo/4.6.2/sysroots/fremantle-arm-sysroot-20.2010.36-2-slim/opt/qtm12/include/QtConnectivity$ ls
Alternative
QBluetoothTransferReply
QNdefNfcUriRecord
QBluetoothAddress
QBluetoothTransferRequest  
QNdefRecord
QBluetoothDeviceDiscoveryAgent   
QBluetoothUuid             
QNearFieldManager
QBluetoothDeviceInfo             
...
On all the other qtm-12 modules, you'd have both the CamelCase and the actual headers in those directories, except for QtConnectivity. Is that it? Any hints on what I'm doing wrong?
Just putting the headers there (from the source) didn't work as a charm and looks bad.

Any help appreciated! (And thanks for qtm-12!)
__________________
Happy n900 owner!
Check my apps: n900fly, accdisplay and the "desktop command execution" widget!

Last edited by cpscotti; 2011-06-29 at 01:02. Reason: missed some words in there.. (and I even used preview)..
 

The Following User Says Thank You to cpscotti For This Useful Post: