Yes, this was indeed the problem. A working manifest is: <Bundle-NativeCode> natives/windows/x86/lwjgl32.dll; natives/windows/x86/OpenAL32.dll; natives/windows/x86/jemalloc32.dll; natives/windows/x86/glfw32.dll; osname=Windows; processor=x86,
natives/windows/x86_64/lwjgl.dll; natives/windows/x86_64/OpenAL.dll; natives/windows/x86_64/jemalloc.dll; natives/windows/x86_64/glfw.dll; osname=Windows; processor=x86-64, natives/linux/x86_64/liblwjgl.so; natives/linux/x86_64/libopenal.so; natives/linux/x86_64/libjemalloc.so; natives/linux/x86_64/libglfw.so; osname=Linux; processor=x86-64, natives/osx/x86_64/liblwjgl.dylib; natives/osx/x86_64/libopenal.dylib; natives/osx/x86_64/libjemalloc.dylib; natives/osx/x86_64/libglfw.dylib; osname=MacOSX; processor=x86-64 </Bundle-NativeCode> Thanks very much for catching this. On first glance, this seems like an issue that bnd could catch. Maybe there's more to it than I think, though... M
pgpkjhFIoFIDg.pgp
Description: OpenPGP digital signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
