Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Thu, 30 Mar 2000 21:14:26 -1000 (HST) From: Jimen Ching To: cygwin@sourceware.cygnus.com Subject: Re: missing prototypes in io.h In-Reply-To: <200003310353.VAA02386@hp2.xraylith.wisc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 30 Mar 2000, Mumit Khan wrote: >I'm confused -- io.h has nothing to do with Win32 API. Cygwin provides an >io.h that is Cygwin specific, and Mingw provides one that is MS runtime >specific, and neither is needed if your code uses Win32 API. >Why don't you tell us what you're looking for, and we can go from there. I wrote a program that uses the cygwin UNIX layer. I need to link this application to a library that was written for Win32. My program compiles with cygwin, no problems. When I tried to compile the library using cygwin, it includes io.h and wants the 'access' function prototype. But io.h (non-mingw32 version) has almost nothing in it. I'm compiling the source of both without the mingw32 option. Thus, gcc does not look into the mingw32 header directory. Am I supposed to compile the library using mingw32, and my program with non-mingw32? I was under the impression that I can write an application that uses both the Win32 API _and_ the cygwin UNIX layer. But the header files seem to stand in the way... --jc -- Jimen Ching (WH6BRR) jching@flex.com wh6brr@uhm.ampr.org -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com