Re: [equinox-dev] looking up binaries

[BJ Hargrave <hargrave@xxxxxxxxxx>]

You can certainly construct Req/Cap relationships
between bundle to ensure they a provisions and resolved together. But that
does not help in actually loading the native code. System.loadLibrary still
needs to be called.

The only thing that might help would
be for the framework to eagerly load all the native libs in the selected
Bundle-NativeCode clause as part of the resolve process for a bundle. That
is, the framework itself would call System.loadLibrary on all the native
libs. There is an ordering issue, but I guess you could load them in the
order they appear in the selected Bundle-NativeCode clause. Any later calls
to System.loadLibrary by the bundle would be no-ops.

--

BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargrave@xxxxxxxxxx

office: +1 386 848 1781 mobile: +1 386 848 3788

From:      
 Scott Lewis <slewis@xxxxxxxxxxxxx>
To:      
 Equinox development
mailing list <equinox-dev@xxxxxxxxxxx>, 
Date:      
 2012/06/10 19:54
Subject:    
   Re: [equinox-dev]
looking up binaries
Sent by:    
   equinox-dev-bounces@xxxxxxxxxxx

---

Could capabilities be used to represent dependencies between
native libraries?  

Scott

On 6/10/2012 2:23 PM, BJ Hargrave wrote: 
'cause that is the way it was designed
in Java? System.loadLibrary is typically called from some class' static
initializer to define the native methods of the class. System.loadLibrary
calls ClassLoader.findLibrary to request advice in locating the native
library. For bundle class loaders, this can then provide the location of
the native library mentioned in the bundle's Bundle-NativeCode manifest
header. 

In your example, since a class in bundle 1 has a static initializer calling
System.loadLibrary("1"), then that code needs to first trigger
a class loader from bundle 2 where  that class' static initializer
calls System.loadLibrary("2"). This will then make sure lib2.so
is loaded before lib1.so. 

In general, the native code support in Java is really only useful for loading
JNI native libraries. How the dependencies of the JNI native libraries
are met is not addressed. 

--

BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargrave@xxxxxxxxxx

office: +1 386 848 1781 mobile: +1 386 848 3788

From:        Pascal
Rapicault <pascal@xxxxxxxxxxxxx>
To:        Equinox
development mailing list <equinox-dev@xxxxxxxxxxx>,
Date:        2012/06/10
16:48 
Subject:        [equinox-dev]
looking up binaries 
Sent by:        equinox-dev-bounces@xxxxxxxxxxx

---

Hey, 

I have a situation where the binaries for my application are spread across
multiple bundles and those libraries depend on each others. For example,
I have bundle1 that carries lib1.so and I have bundle2 that carries lib2.so,
and bundle1 depends on bundle2. When I try to load lib1.so if lib2.so has
not yet been loaded, then the loading of lib1 will fail.

Is there a fundamental reason why we loading of the libraries could mimic
the loading of classes?

Thx

Pascal

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev




_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev