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:	<3F2B292B.3020600@santafe.edu>
Date:	Fri, 01 Aug 2003 20:59:55 -0600
From:	"Marcus G. Daniels" <mgd AT santafe DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: loading DLLs created with Cygwin into Sun JDK

Alan Thompson write:

> OK - now you have me confused....
> If you're not loading DLL's into Java for use with JNI, what are you doing?
> Also, note that those techniques work for both plain JNI (i.e. java calls into C/C++) as well as the invocation API (where a C/C++ program creates an JVM).

Again, "those techniques" specify use of -mno-cygwin, which worked fine for me in my 
posted example.  The crash happens as the DLL is loaded, not when methods are called.

Have you actually tried _not_ using -mno-cygwin?

Also, using 'javah' or not to generate the headers (and making sure JNIEXPORT and
JNICALL are in the header and implementation declarations, and using
and using -Wl,--add-stdcall-alias makes no difference.  For this simple test case, you 
need to have JNIEXPORT/JNICALL and the -Wl,--add-stdcall-alias, or neither to get the 
test case to work.  





--
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/

- Raw text -