This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: new to-do item
- To: "Fish" <fish at infidels dot org>,<cygwin at cygwin dot com>
- Subject: RE: new to-do item
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Tue, 17 Jul 2001 14:45:39 +1000
> -----Original Message-----
> From: Fish [mailto:fish@infidels.org]
> Sent: Tuesday, July 17, 2001 2:49 PM
> To: cygwin@cygwin.com
> Subject: RE: new to-do item
>
> > As I said, this is a missing header file or import library
> > issue. The header files and libraries come with the
> > cygwin distribution but they are not related to the Cygwin
> > DLL.
>
> I think I now see the source of my original confusion. Cygwin
> DLL code must
> obviously make certain Win32 API calls (in order to emulate
> the *ix environment)
> and purely as a side effect of that, it allows one to write
> code that makes the
> same API calls.
Nope. Wrong again.
Some terms -
the cygwin dll - a dll that exposes a subset of the common unix API
calls.
Cygwin-the-distribution - a compiler,linker,many utilities and the
cygwin dll
> But the ability to have one's code be able to make Win32 API
> calls isn't
> supported per se. It's simply one of the side effects. Is
> that correct?
Nope. They are orthogonal. You make win32 API calls by linking against a
win32 API exposing dll - say msvcrt.dll or kernel32.dll. That is how you
make those calls _WHETHER OR NOT_ you link against cygwin1.dll.
> Thus, as you have now sufficiently explained, my original
> request to include the
> ability to make a given Win32 API call was inappropriate for
> the Cygwin DLL TODO
> list. I understand that now.
It's inappropriate for the cygwin dll TODO because it's an orthogonal
issue. It's like reporting a bug with vim on the TODO.
It is _entirely_ appropriate to discuss the missing export for the
open-source w32api package :]
Rob
--
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/