Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <20010612172714.16885.qmail@mail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
From: "D G" <dgun AT umpire DOT com>
To: cygwin AT cygwin DOT com
Date: Wed, 13 Jun 2001 01:27:14 +0800
Subject: header files and FILE struct

I'm trying to port a unix application to cygwin, and I have two big questions:

1) When do I use the mingw header files, and when do I use the regular header files?  For example, there are two copies of stdio.h, one in /usr/include/mingw and one in /usr/include, and both are different.  Also, values.h is only in mingw, and the application wants this header file--is it safe to include it as <mingw/values.h>?

2) The application makes use of FILE struct internals, but these are not defined in stdio.h.  How do I work around the FILE->_IO_read_ptr and FILE->_IO_read_base usage?  It looks like cygwin uses some __sFILE structure instead of the _IO_FILE struct from linux.

The application compiles and runs fine on linux.

-- 

_______________________________________________
Make PC-to-Phone calls with Net2Phone.
Sign-up today at: http://www.net2phone.com/cgi-bin/link.cgi?121




--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple