Usage ===== BlueCove on Linux consists of three parts, a main "bluecove.jar" file (Apache Software License 2.0 that implements JSR-82, a "bluecove-gpl.jar" file (GPLv3+) that implements a BlueCove backend for interfacing with the Linux BlueZ stack and a "bluecove-bluez.jar" that uses DBUS to communicate For your applications to work you should thus include two JAR files in your classpath: /usr/share/java/bluecove.jar AND ( /usr/lib/bluecove/bluecove-gpl.jar # on i386 or ppc /usr/lib64/bluecove/bluecove-gpl.jar # on x86_64 or ppc64 OR /usr/lib/bluecove/bluecove-bluez.jar # on i386 or ppc /usr/lib64/bluecove/bluecove-bluez.jar # on x86_64 or ppc64 OR /usr/share/java/bluecove-emu.jar # for the emulator ) The bluecove-gpl.jar and bluecove-bluez.jar load a system library that is also located in the library directory. In case you use bluecove-bluez (device discovery using DBUS) you also need to have "libmatthew-java" and "dbus-java >=2.5.1" installed and added to the classpath of your application. In case you want to use the emulator you need "microemulator" (http://www.microemu.org) installed. See http://www.bluecove.org/bluecove-emu/ You can use the "build-classpath" script to generate the classpath for the bluecove and bluecove-emu JARs: java -cp `build-classpath bluecove bluecove-emu` package.className This unfortunately doesn't work for bluecove-gpl and bluecove-bluez because they are located in a architecture dependent directory, /usr/lib or /usr/lib64 (see above). In case you use "bluecove-bluez" you also need to add "dbus-java" and "libmatthew-java" to your classpath: java -cp `build-classpath bluecove dbus-java`:\ /usr/lib64/libmatthew-java/unix.jar:\ /usr/lib64/libmatthew-java/hexdump.jar:\ /usr/lib64/bluecove/bluecove-bluez.jar \ package.className (remove the 64 from lib64 on 32 bit machines) Javadoc ======= This library implements JSR-82. The "official" API documentation can be found on http://jcp.org/en/jsr/detail?id=82. As a programmer you should only rely on this API.