Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <00ce01c2be47$024336b0$2301a8c0@yaccom.com>
From: "gilles BOURGEOIS" <gbourgeois AT yaccom DOT com>
To: "friedman_hill ernest j" <ejfried AT ca DOT sandia DOT gov>, <cygwin AT cygwin DOT com>
References: <200301171627 DOT IAA03968 AT ca DOT sandia DOT gov>
Subject: Re: Using cygwin and JAVA/JNI
Date: Fri, 17 Jan 2003 17:39:30 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MDRemoteIP: 192.168.1.35
X-Return-Path: gbourgeois AT yaccom DOT com
X-MDaemon-Deliver-To: cygwin AT cygwin DOT com

thanks a lot,
actually, with -Wl,--add-stdcall-alias to the gcc line, all worked fine.



----- Original Message -----
From: "friedman_hill ernest j" <ejfried AT ca DOT sandia DOT gov>
To: <cygwin AT cygwin DOT com>
Sent: Friday, January 17, 2003 5:27 PM
Subject: Re: Using cygwin and JAVA/JNI


>
> Randall is usually 100% right about everything, but here he's actually
> not. I haven't done it in a long time, but I've certainly written JNI
> libraries with cygwin -- and in fact, used some fairly cygwin specific
> features in doing so (my JNI library explicitly used dlopen() to open
> another library, as I recall, and it all worked; and furthermore, much
> of my library was written in C++, but the JNI entry points were
> exported as 'extern "C".') I was amazed and thrilled when it all
> worked.
>
> When I did this, Mumit Khan's web page on the topic was invaluable,
> but cygwin has changed a lot since then, so I'm sure the information
> is out of date. Anyway, you might start by looking at the JNI links
> halfway down this page:
>
>    http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
>
>
> I think Randall R Schulz wrote:
> > Gilles,
> >
> > I don't believe the ABI (application binary interface) used by the
> > Microsoft compilers is compatible with that used by GCC and hence the
Sun
> > JVM, being compiled by the Microsoft tools, cannot access GCC-compiled
> > libraries via JNI.
> >
> > Randall Schulz
> >
> >
> > At 06:41 2003-01-17, gilles BOURGEOIS wrote:
> > >hello
> > >
> > >I wonder if it is possible to use JNI upon a DLL .i.e a shared libray
like
> > >.so file generated with gcc, without the mno-cygwin option. (my lib
uses
> > >IPC SYSTEM V, that is why I rely on the cygwin and cygipc libraries) I
am
> > >not a newbie with java/jni or gcc, but mixing all of them seems to
crash
> > >the JVM. Of course, It works if the library is generated with gcc under
> > >linux but if executing the whole program (JVM instantiate) under
cygwin,
> > >it fails. Any one ever performed such a tricky architecture? thanks
> > >
> > >gilles
> >
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
>
>
>
> ---------------------------------------------------------
> Ernest Friedman-Hill
> Distributed Systems Research        Phone: (925) 294-2154
> Sandia National Labs                FAX:   (925) 294-2234
> PO Box 969, MS 9012                 ejfried AT ca DOT sandia DOT gov
> Livermore, CA 94550         http://herzberg.ca.sandia.gov
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/