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
From: "Fish" <fish AT infidels DOT org>
To: <cygwin AT cygwin DOT com>
Subject: RE: new to-do item
Date: Mon, 16 Jul 2001 21:03:20 -0700
Message-ID: <000501c10e75$6a5b10c0$0200a8c0@proteva>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <20010716232435.A6474@redhat.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

> >Is this not a cygwin dll issue?
>
> No.  The Cygwin DLL emulates *UNIX*, not Windows.

Hmmm... Yes, I suppose you're right in that regard.

> We don't add Windows system calls to the Cygwin DLL.

So what you're basically saying then is one can *only* use Cygwin to develop
UNIX programs that should also be able to run on Windows platforms as well, BUT,
even though these programs just so happen to be able to be run under Windows,
they are not allowed to make use of *any* Windows API calls whatsoever anywhere
in their code?? Is that correct?

> >If it's not, then *WHO'S* issue is it??
>
> It's either a header file or import library issue.
>
> I've cc'ed this email to the cygwin mailing list.  Perhaps
> someone will be willing to research what needs to be
> done to add this missing function or macro.
>
> cgf

Thanks. The development team of which I'm a part of  (as is Greg Smith too) has
been for the most part successful so far in developing a product that, with
cygwin's help, runs as easily on Windows as it does on Linux/Unix (*ix)
platforms. Unfortunately, however, it doesn't perform as well under Windows as
it does under *ix. We attribute this poor performance for the most part to the
cygwin code.

We fully understand, of course, that emulating an *ix environment on Windows is
no easy task, and applaud the cygwin people for doing as good a job as they have
in accomplishing that end.

But in order to reach the desired performance level under Windows (*without*
having to rewrite it completely in native Win32 form), we would like to
introduce on an as-needed basis certain Win32-specific logic in a few places.
From what you're telling me, cygwin doesn't allow (support) that.

If we are unable to do that (i.e. make native Win32 API calls wherever we feel
it's necessary) using the cygwin development environment, then forgive me but
I'm at a total loss as to how to accomplish our desired goal (short of rewriting
it completely in native Win32 using Microsnot's own tools; i.e. developing a
custom "Win32-ONLY" version).

Is there *any* way, using cygwin, to make calls to Win32 APIs?

Thanks.

(If there's a more appropriate email list or news group for such questions,
please let me know. I know you're a busy man and I don't wish to take up your
time if you're not the right person to be talking to regarding this issue.)

Sincerely,
--
"Fish" (David B. Trout)
   fish AT infidels DOT org


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