I was watching the checkins yesterday and saw that get cleaned up.
But here is what I'm seeing on OS X (and note that I'm a linux developer moving to OS X, so some of this on OS X is still new to me).
1. I had to add the include path to jni.h to the build.xml (perhaps there was an easier way)
2. This creates a libjlibnxt.dynlib not libjlibnxt.so
3. I keep get jlibnxt not found
4. I haven't even tried to tackle bluez vs. apple's built in Bluetooth API
I spent a good chunk of last night trying to search google for how to deal with JNI libraries on OS X. dynlib vs jnilib, dynamic library vs. bundles and tried a lot of combinations. I came up empty. If I can find the time today I will try to look at the way that they rxtx folks dealt with making the OS X JNI library, but it appears that it was a fork and used the XCode system (from a very brief look at the directory structure). The rxtx library is also universal (includes both ppx and intel).
Ships are safe inside the harbor.