<html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi everyone, Today I started work on the bluetooth code, specifically on the linux server code. I'm basing most of my code on what is done in the bluecove library (APL, written in Java with some C). I.e. most things go via dbus, and the C sockets API is used for actual communication (I believe Android uses the same methodology internally). I have had two issues: - Linking against glib: specifically I'm using the gio portion of glib for dbus: in the makefile I need to add gtk in the use_externals part of the makefile, having only glib causes linking to fail. Is this expected? - Including the bluez headers: (I've initially used pkg-config to include them -- I still need to look into how I would include them correctly). These headers are part of bluez, and have GPL notices -- I am however only using them for structs and constants, and not linking, as is done both for Android and for Bluecove. The Android sources include "cleaned" headers, which can be found e.g. here: <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://gitorious.org/0xdroid/system_bluetooth/trees/59ca0be6dc8ef3f30f8f863d8fb805a55bf12fe5/bluez-clean-headers/bluetooth">http://gitorious.org/0xdroid/system_bluetooth/trees/59ca0be6dc8ef3f30f8f863d8fb805a55bf12fe5/bluez-clean-headers/bluetooth</a> . Would it be worth including these headers in the LO sources, to save the need to install the appropriate library to compile LO (bluez-libs-devel on fedora)? I'm assuming that the android & bluecove interpretation is correct and I can still use these without GPL issues? Cheers, Andrzej </body> </html>