Mail Archives: cygwin/2000/03/31/10:42:06
At 02:14 AM 3/31/00, Jimen Ching wrote:
>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...
io.h is a Windows/DOS concoction. Look for access() in the Cygwin headers
and use that for non-Windows compilers (I don't remember the header file it
comes from off the top of my head...)
Larry Hall lhall AT rfk DOT com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
(508) 560-1285 - cell phone
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -