Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 1 Dec 2004 11:32:41 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Compile within cygwin with -mnocygwin
Message-ID: <20041201163241.GF13804@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
References: <4DEA5E615F52DD4F9D9C6C2D70FCE63B0120132F@esmexc02.emea.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DEA5E615F52DD4F9D9C6C2D70FCE63B0120132F@esmexc02.emea.cpqcorp.net>
User-Agent: Mutt/1.4.1i

On Wed, Dec 01, 2004 at 04:23:55PM +0100, BARTHEL, MATTIAS wrote:
>Hello
>
>I am trying to compile a perl swig1.3 wrapper for a C++ lib
>using cygwin but with the compiler define -mno-cygwin.
>
>In perl.h there are lots of includes that cannot be found.

Right.  You have just discovered the difference between "no cygwin"
and "cygwin".  "Cygwin" provides a unix-like environment for windows.

"No cygwin" provides a windows-like environment for windows with
a few minor, cheap unixisms thrown in.  netinet/in.h, sys/ioctl.h,
etc., are not minor or cheap so they are not part of "no cygwin".

cgf

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