[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Linux Core Fragments
|
Thanks guys. So, unless anyone objects, I'll proceed and create fragments
for the different Linux architectures and keep the original fragment for
the source and the shared Java jars.
Doug Schaefer, Technical Lead, Eclipse CDT
Ottawa Lab, IBM Canada, Rational Software Division
Tom Tromey <tromey@xxxxxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx
10/08/2004 12:29 PM
Please respond to
cdt-dev
To
cdt-dev@xxxxxxxxxxx
cc
Subject
Re: [cdt-dev] Linux Core Fragments
>>>>> "Ben" == Ben Konrath <bkonrath@xxxxxxxxxx> writes:
Ben> As far as I understand it, System.loadlibrary will look in your
system
Ben> library paths. Eclipse overrides this and looks in
Ben> <plugin>/os/<platform>/<arch> first (ie
Ben> org.eclipse.core.resources.linux/os/linux/x86).
System.loadLibrary asks the requesting class' ClassLoader. See
ClassLoader.findLibrary(). The default returns null, which falls
back to whatever System wants.
In Eclipse 2, the plugin class loader implemented this method and had
it search the plugin directory. It had a list of places to look,
based on the OS, the architecture, and the window system. In Eclipse
3 it is similar, though I'm not really familiar with that code.
Tom
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev
