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:	<01C1054C.844D5B00.jorgens@coho.net>
From:	Steve Jorgensen <jorgens AT coho DOT net>
Reply-To:	"jorgens AT coho DOT net" <jorgens AT coho DOT net>
To:	"cygwin AT cygwin. Com (E-mail)" <cygwin AT cygwin DOT com>
Subject:	RE: Cygwin 2.1 and Python modules
Date:	Thu, 5 Jul 2001 12:17:30 -0700
X-Mailer:	Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version:	1.0

-----Original Message-----
From:	Jason Tishler [SMTP:Jason DOT Tishler AT dothill DOT com]
Sent:	Thursday, July 05, 2001 11:33 AM
To:	David Abrahams
Cc:	Cygwin
Subject:	Re: Cygwin 2.1 and Python modules

Dave,

...
It takes advantage of somewhat recent Cygwin gcc enhancements:

    1. binding to msvcrt.dll instead of crtdll.dll
    2. ability to link directly to a DLL (instead of requiring an import
       library)

I recently printed the section of the Cygwin User's Guide, and it appears 
to show only the import-library method of linking to a DLL (if I understand 
what I'm seeing).  I suppose it's important to keep it there since some 
users may freeze their Cygwin installations for periods of time, but it 
would be nice to have an example of the new way in the document as well.

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

- Raw text -