From: Andrew Mickish <mickish@cmu.edu>
To: "S. Suchitra" <srinis@caip.rutgers.edu>
Cc: gnu-win32@cygnus.com
Subject: Re: JNI with Cygwin32
Date: Fri, 16 Oct 1998 06:08:00 -0000 [thread overview]
Message-ID: <36269957.9C390267@cmu.edu> (raw)
In-Reply-To: <199810151709.NAA17198@caip.rutgers.edu>
One thing that I don't recall mentioning in any of my previous posts is that
editing one of the Java header files is necessary. I guess VC++ defines a type
called __int64, which is not defined in the gcc header files. In your jdk
directory, change include/win32/jni_md.h to look like this:
#define JNIEXPORT /*__declspec(dllexport)*/
#define JNICALL __stdcall
typedef long jint;
typedef long /*__int64*/ jlong;
typedef signed char jbyte;
Maybe someone else can say whether this is actually an oversight in the gcc
header files.
The line above about declspec has to do with the different ways that VC++ and
gcc export functions from DLLs. VC++ uses a simple keyword, but gcc has a
convoluted linking procedure based on an init.cc file. I have been subscribed
to the list for months hoping to hear justification for this, or the
announcement of a simplified procedure, but haven't heard anything yet.
If you send me a trace of your remaining errors I will see if I recognize
anything.
--Andrew Mickish
S. Suchitra wrote:
> Hi,
>
> I have been reading your messages on the Cygwin32 mailing list
> about getting JNI to work with gcc on the Cygnus Win32 interface.
> I downloaded your zip file with the HelloWorld example. However I am
> not able to compile it using your Makefile..it seems to be giving a
> number of parse and syntax errors in header files like jni.h and some other
> files in the Cygwin32 library.
>
> I was wondering whether you also had similar problems and how you overcame
> them. I would really appreciate any pointers you may be able to give me.
> I am working on a Windows Nt 4.0 machine with Cygnus Win 32 19.1 release.
>
> Thanking you,
> Suchitra.
>
> srinis@caip.rutgers.edu
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next parent reply other threads:[~1998-10-16 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199810151709.NAA17198@caip.rutgers.edu>
1998-10-16 6:08 ` Andrew Mickish [this message]
1998-10-22 15:51 ` Timothy Baldwin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36269957.9C390267@cmu.edu \
--to=mickish@cmu.edu \
--cc=gnu-win32@cygnus.com \
--cc=srinis@caip.rutgers.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).