Re: GCJ Native Proposal
- To: debian-java@lists.debian.org
- Subject: Re: GCJ Native Proposal
- From: Jerry Haltom <wasabi@larvalstage.net>
- Date: Sat, 12 Mar 2005 13:06:10 -0600
- Message-id: <1110654370.9890.22.camel@localhost.localdomain>
- In-reply-to: <1110654285.9890.21.camel@localhost.localdomain>
- References: <1110654285.9890.21.camel@localhost.localdomain>
Disregard this. I accidentally hit send. I am still finishing it. =(
On Sat, 2005-03-12 at 13:04 -0600, Jerry Haltom wrote:
> Attention Java Maintainers: This Effects You
>
>
> This is a recap of an ad-hoc discussion a number of Java maintainers had
> a few minutes ago in #debian-java concerning our direction with regards
> to including native GCJ compiled Jar files in our packages.
>
> Brief overview: gcj-4.0 is now in experimental. What it gives us is the
> ability to package native binary .so files along side their .jar
> counterparts for usage with gij (the GCJ interpreter, a virtual
> machine). When these .so files are present (in the correct location,
> registered with the correct mechanism) gij will load them automatically
> and use them in the place of the corresponding .jar file. The main
> motivation for this is speed. There is no JIT overhead involved and it
> runs native, not interpreted.
>
> This begs the question then: How do we make these native .so files
> available in our packages to our users. A number of ideas were
> considered:
>
> a) Include the .so along with the .jar in the same deb.
> b) Create a separate package for the .so.
>
> The first one (a) can be discounted because it would convert every Java
> package into a binary: arch package. This isn't feasible for obvious
> reasons: we like archive space!
>
> The second one
>
> --
> Jerry Haltom <wasabi@larvalstage.net>
>
>
--
Jerry Haltom <wasabi@larvalstage.net>
Reply to: