I've submitted a patch that fixes this (bug request 147885). The Makefile currently builds libraries and places them in the directories os/macosx/ppc/ and os/macosx/x86/. These libraries are not universal binaries. Would it work to simply create one universal set of libraries and place them in os/macosx/? Which way is preferable (two separate arch directories or one universal)?
Cheers, Craig
On Dec 10, 2006, at 6:36 PM, Andrew Niefer wrote:
The library is never added to the java.library.path. It is up to the class loader to find the library when System.loadLibrary is called. The java.library.path is how the normal java classloader does it.
In Eclipse, the BundleClassloader takes care of finding the library. For the bundle and its fragments it delegates to the ClassLoadingHook's, and I believe the default is the EclipseClassLoadingHook, which looks under a set of directories:
/ws/<ws>/
/os/<os>/<arch>
/os/<os>
/nl/<nl>...
/
-Andrew
I've been puzzling over this for a while without success. Does anyone
know how the architecture-specific directory containing libpty and
libspawner gets added to the java.library.path so that
System.loadlibrary("spawner") succeeds? Or is somehow everything
under the plugins directory automatically searched?
Thanks,
Greg
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ cdt-dev mailing list
|
