Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 17 Sep 2004 14:42:23 +0200
From: "Gerrit P. Haase" <gp AT familiehaase DOT de>
Reply-To: "Gerrit @ cygwin" <cygwin AT cygwin DOT com>
Organization: Esse keine toten Tiere
Message-ID: <1729140505.20040917144223@familiehaase.de>
To: "Grzegorz B. Prokopski" <gadek AT debian DOT org>
CC: cygwin AT cygwin DOT com, sablevm-user AT sablevm DOT org, sablevm-devel AT sablevm DOT org
Subject: Re: Is cygffi.dll needed for SableVM JVM?
In-Reply-To: <1095382062.1234.164.camel@gadek.homelinux.org>
References: <20040906021844 DOT 84591 DOT qmail AT web53304 DOT mail DOT yahoo DOT com> <1095382062 DOT 1234 DOT 164 DOT camel AT gadek DOT homelinux DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hello Grzegorz,

Am Freitag, 17. September 2004 um 02:47 schriebst du:

> The most tricky part (for me, at the time I didn't know much about
> Cygwin) was getting a shared library of libffi.  SableVM currently
> does not allow for static compilation, so we needed to compile
> /bin/cygffi.dll ourselves.  Once that was done - the rest was easy.
> This was acceptable as an experiment, but in the long run we'd like to
> have a Cygwin package of SableVM, so we need a cleaner method. [*]

> There's two possible solutions I can see:
> 1. include shared library of libffi into official cygwin gcc-java
> (along with ffi headers)
> 2. make libsablevm link against statically compiled libffi.

> I am not sure 2) is possible and I don't know how to do it.  SableVM
> consists of 3 binary parts: /usr/bin/sablevm binary wrapper that loads
> libsablevm which in turn loads via ltdl_open JNI libraries from
> sablevm-classpath.  In such scenario, would it be possible for
> libsablevm to link against static libffi?  How to accomplish that
> in practice? (we use auto* and libtool in the build process)
> Some good advice or RTFM URLs are welcome.

> If 2) is not possible, would it be possible for gcc maintainer
> to include shared version of libffi in gcc-java?

You can link against static archives when using 'pass_all' instead of
'file_magic ^x86 archive import|^x86 DLL' to recognise dependent
libraries in libtool (change in libtool.m4).


> [*] We have a machine that could serve as an autobuilder for
> Cygwin packages, so once we make SableVM buildable and working
> under Cygwin it should be possible to ensure every new version
> still works.




-- 
=^..^=



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/