Nice work on the API, it looks like its going to be great to work with, nice to see someone offering native support for an obex push rather than having to rely on 3rd party tools like some of the other API's I've seen.
However I'm recieving the following error when trying to install it on my Debian box, i have the latest versions of GCC, Bluez, PyBluez and the other bits, i cant think that I'm missing anything.
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.4 -c src/linux/lightblue_util.c -o build/temp.linux-i586-2.4/src/linux/lightblue_util.o
src/linux/lightblue_util.c:28:20: error: Python.h: No such file or directory
src/linux/lightblue_util.c:30:33: error: bluetooth/bluetooth.h: No such file or directory
src/linux/lightblue_util.c:31:27: error: bluetooth/hci.h: No such file or directory
src/linux/lightblue_util.c:32:31: error: bluetooth/hci_lib.h: No such file or directory
src/linux/lightblue_util.c:37: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
src/linux/lightblue_util.c:60: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
src/linux/lightblue_util.c:86: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
src/linux/lightblue_util.c:107: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'utilmethods'
src/linux/lightblue_util.c: In function 'init_lightblueutil':
src/linux/lightblue_util.c:116: warning: implicit declaration of function 'Py_InitModule'
src/linux/lightblue_util.c:116: error: 'utilmethods' undeclared (first use in this function)
src/linux/lightblue_util.c:116: error: (Each undeclared identifier is reported only once
src/linux/lightblue_util.c:116: error: for each function it appears in.)
error: command 'gcc' failed with exit status 1
Any ideas what may be causing this issue? I'm planning to integrate this with one of my other applications and the mac and channel will be hard coded, so I'm un likely to need all the general scanning buggins, just the object push stuff, Will it be easy for me to strip the app down a little bit, so its a sort of 'low fat' version with purely an obex push api i can use?
Thanks buds,
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure if this makes too much differance, but perhaps the issue is caused by the fact that bluez 3.7 and above run with libbluetooth2 and not version 1, I saw you've mentioned that before.
Thanks,
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not sure about the bluez/libbluetooth2 issue - but are you saying you've installed the libbluetooth1-dev, bluez-utils, and libbluetooth1 packages already and you're still getting these errors?
Looks like it can't find any of the Python headers either... have you got the python-dev package? (Or perhaps it's something like python2.3-dev)
> Will it be easy for me to strip the app down a little bit, so its a sort of 'low fat' version with
> purely an obex push api i can use?
Not sure what you mean?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for getting back to me mate. I do indeed seem to have all the debian packages installed, I'm running on Python 2.5 along with Bluez3.9 utils and libs. The debian package for the bluez seemed to install libbluetooth1-dev, bluez-utils, and libbluetooth1 as dependancies, but I'll try and install them manualy again and see if that helps.
Dont worry too much about the 'low fat' bit, It's just that I dont need any of the discovery processes from the API as I already know the mac and channel for the device I'm connecting to and it'll be iether hard coded or pulled from an XML file so I'll only be needing the ObexPush functions from the API, I was thinking that perhaps I could strip out the stuff I dont need from the source and compile a lighter version that I can place on my box as every last little nugget of memory is priceless at the moment :-D
I'll have a go at installing these depencancies myself, Have you got an exact list of what is required? or is the list you gave above pretty much it?
Thanks again,
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Managed to sort this problem, the Python headers were not installed properly, I stuck them on along with the open obex-dev package and its pretty much working a charm for pushing files.
Thanks,
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's great - and about cutting down the source, there's not much to cut out in terms of device discovery code in lightblue, because it mainly uses the discovery functions from the pybluez library - so you'd really have to look at cutting that down instead. The only thing you could remove from the lightblue source is probably the _discoveryui.py file which is used for
selectdevice() and selectservice().
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Chaps,
Nice work on the API, it looks like its going to be great to work with, nice to see someone offering native support for an obex push rather than having to rely on 3rd party tools like some of the other API's I've seen.
However I'm recieving the following error when trying to install it on my Debian box, i have the latest versions of GCC, Bluez, PyBluez and the other bits, i cant think that I'm missing anything.
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.4 -c src/linux/lightblue_util.c -o build/temp.linux-i586-2.4/src/linux/lightblue_util.o
src/linux/lightblue_util.c:28:20: error: Python.h: No such file or directory
src/linux/lightblue_util.c:30:33: error: bluetooth/bluetooth.h: No such file or directory
src/linux/lightblue_util.c:31:27: error: bluetooth/hci.h: No such file or directory
src/linux/lightblue_util.c:32:31: error: bluetooth/hci_lib.h: No such file or directory
src/linux/lightblue_util.c:37: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
src/linux/lightblue_util.c:60: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
src/linux/lightblue_util.c:86: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
src/linux/lightblue_util.c:107: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'utilmethods'
src/linux/lightblue_util.c: In function 'init_lightblueutil':
src/linux/lightblue_util.c:116: warning: implicit declaration of function 'Py_InitModule'
src/linux/lightblue_util.c:116: error: 'utilmethods' undeclared (first use in this function)
src/linux/lightblue_util.c:116: error: (Each undeclared identifier is reported only once
src/linux/lightblue_util.c:116: error: for each function it appears in.)
error: command 'gcc' failed with exit status 1
Any ideas what may be causing this issue? I'm planning to integrate this with one of my other applications and the mac and channel will be hard coded, so I'm un likely to need all the general scanning buggins, just the object push stuff, Will it be easy for me to strip the app down a little bit, so its a sort of 'low fat' version with purely an obex push api i can use?
Thanks buds,
Rob
I'm not sure if this makes too much differance, but perhaps the issue is caused by the fact that bluez 3.7 and above run with libbluetooth2 and not version 1, I saw you've mentioned that before.
Thanks,
Rob
Hi Rob,
Not sure about the bluez/libbluetooth2 issue - but are you saying you've installed the libbluetooth1-dev, bluez-utils, and libbluetooth1 packages already and you're still getting these errors?
Looks like it can't find any of the Python headers either... have you got the python-dev package? (Or perhaps it's something like python2.3-dev)
> Will it be easy for me to strip the app down a little bit, so its a sort of 'low fat' version with
> purely an obex push api i can use?
Not sure what you mean?
Morning Blam,
Thanks for getting back to me mate. I do indeed seem to have all the debian packages installed, I'm running on Python 2.5 along with Bluez3.9 utils and libs. The debian package for the bluez seemed to install libbluetooth1-dev, bluez-utils, and libbluetooth1 as dependancies, but I'll try and install them manualy again and see if that helps.
Dont worry too much about the 'low fat' bit, It's just that I dont need any of the discovery processes from the API as I already know the mac and channel for the device I'm connecting to and it'll be iether hard coded or pulled from an XML file so I'll only be needing the ObexPush functions from the API, I was thinking that perhaps I could strip out the stuff I dont need from the source and compile a lighter version that I can place on my box as every last little nugget of memory is priceless at the moment :-D
I'll have a go at installing these depencancies myself, Have you got an exact list of what is required? or is the list you gave above pretty much it?
Thanks again,
Rob
Hey Blam,
Managed to sort this problem, the Python headers were not installed properly, I stuck them on along with the open obex-dev package and its pretty much working a charm for pushing files.
Thanks,
Rob
That's great - and about cutting down the source, there's not much to cut out in terms of device discovery code in lightblue, because it mainly uses the discovery functions from the pybluez library - so you'd really have to look at cutting that down instead. The only thing you could remove from the lightblue source is probably the _discoveryui.py file which is used for
selectdevice() and selectservice().