felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall" <he...@ungoverned.org>
Subject Re: Sigil progress
Date Fri, 07 Aug 2009 14:51:42 GMT
On 8/7/09 10:44, David Savage wrote:
> Bizarrely we're having a similar internal conversation here at Paremus
> about other native libraries the issue (courtesy of Holger Hoffstatte)
> is related to this one:
> https://www.osgi.org/bugzilla/show_bug.cgi?id=38
> So perhaps I won't hold my breath...

Unfortunately, that is not easy to resolve. Once you get into native 
code and the native code needs a native library, then OSGi is no longer 
under control, so it doesn't get asked. The only solution is to extract 
native libraries from bundles in platform-specific ways to make them 
available to the operating system. That could further open up issues 
with respect to dynamism, however.

Luckily, I think the SWT thing is easier to resolve.

> Would be good not to create hundreds of command line launchers if one
> simple one will do most of what we want...From the sigil side I just
> need a relatively stable launcher that allows me to say to say install
> this, start that etc.

Actually, the recent changes I made to the Felix framework launcher were 
a result of my experience with the book launcher, since I found its 
ability to simply install and start bundles in a directory to be handy.

I am looking at modifying Felix' framework launcher to make it use only 
the standard launching API, at which point it would become a slightly 
more complicated version of the generic launcher I just sent to the list 
a couple of messages ago.

-> richard

View raw message