Hi, I am going to deal with this by passing a custom class path for architecture-specific libraries in my Mac mock up of Braille Blaster. Regards, Alex, On 2011-02-01, at 12:57 AM, Michael Whapples wrote: > How does that deal with different architectures? As stated a 64-bit JVM won't > run a 32-bit library. As far as I know all architectures of a given platform > all have the same extensions for their dynamic library extensions (IE. 32-bit > or 64-bit on windows, you still end up using a .dll). > > I think it was the architecture issue which was causing the problem. > > Michael Whapples > On 01/02/11 04:34, John J. Boyer wrote: >> As a matter of fact, the subdirectory native/lib can contain the dynamic >> or shared libraries for all three platforms simultaneously. There will >> be no danger of confusion, because BrailleBlaster will use the library >> extension specific to each platform. This will increase the size of the >> package somewhat, but it might be convenient. >> >> I still have to look at Alex's mockup. However, if one doesn't care >> about an app bundle, it should be possible to run BrailleBlaster on all >> three platforms with just >> java -jar brailleblaster.jar >> >> John >> > >