delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
Date: | Wed, 2 Jun 1999 18:50:45 -0400 |
Message-Id: | <199906022250.SAA02275@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | PositivePi AT aol DOT com |
CC: | cygwin AT sourceware DOT cygnus DOT com |
In-reply-to: | <15ad59a8.248706b9@aol.com> (PositivePi@aol.com) |
Subject: | Re: Staticly linking cygwin1.dll to exe? |
References: | <15ad59a8 DOT 248706b9 AT aol DOT com> |
There's a lot more to cygwin than just the parts you *think* you're using. A lot of the cygwin1.dll code is there to emulate the model Unix uses, so you can do things like "kill", wildcards, or putting programs into the background. If you don't want all this stuff, perhaps you should try mingw? It doesn't have the 400K dll, but then it doesn't have any of that functionality either. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |