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
From: "Mike Bresnahan" <mbresnah AT visi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Using cygwin and JAVA/JNI
Date: Wed, 5 Feb 2003 22:52:17 -0800
Message-ID: <EKEJKOHPOIIALFJMKEIGGEDDEHAA.mbresnah@visi.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
In-Reply-To: <4.3.2.7.2.20030205201711.00b1fb90@mail.alphatech.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

I have been using Cygwin GCC 3.2 to build JNI DLLs that use <iostream>
without difficulty.  I have done the following things:

- put -mno-cygwin -D_REENTRANT -D_GNU_SOURCE -D__int64="long long" on the
compiler command line
- put -mno-cygwin -Wl,--add-stdcall-alias on the linker command line

See the Cygwin FAQ at http://cygwin.com/faq/faq.html for info
on -mno-cygwin.

Mike Bresnahan
> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Alan Thompson
> Sent: Wednesday, February 05, 2003 8:18 PM
> To: cygwin AT cygwin DOT com
> Subject: Using cygwin and JAVA/JNI
>
>
>
> >
> >Hi all - I have been doing some JNI stuff to integrate our
> legacy software, and I have had very good luck following the
> examples at http://www.inonit.com/cygwin/jni/helloWorld/ .  The
> only twist is that I've been using g++ instead of gcc, which
> simplifies the non-java part.
> >
> >Here's a question, though:  I cannot for the life of me figure
> out how to use the C++ <iostream> in any of the code!  For some
> reason, the "-mno-cygwin" flag kills the ability of g++ to either
> compile or link any code referring to <iostream>.  This means one
> is stuck using good old printf(), instead of the more modern way.
>  No matter how I break up the complies, it still fails at the
> linking stage (when -mno-cygwin is still required, according to
> my experiments).
> >
> >Does anyone have any ideas?  Also, I've been unable to find any
> documentation on the -mno-cygwin flag in the gcc/g++ man pages.
> Can anyone point me to where this comes from and/or is documented?
> >
> >Thanks again for all of the help,
> >Alan Thompson
> >
> >P.S.  I've been using Cygwin for quite a while now ant it's
> fantastic when you're chained to a windoze machine....
> >


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