Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] How does libspawner get added to java.library.path?

Great, thanks. Just what I was looking for.

BTW, are there plans to add macosx/x86 to the org.eclipse.cdt.core.macosx fragment? I have built libpty.jnilib and libspawner.jnilib (from HEAD) for this architecture if you'd like copies.

Greg

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



Greg Watson <g.watson@xxxxxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx

12/10/2006 06:28 PM

Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

To
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
cc
Subject
[cdt-dev] How does libspawner get added to java.library.path?





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


Back to the top