Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Jonadab the Unsightly One" Organization: There is no organisation. To: cygwin AT cygwin DOT com Date: Wed, 18 Jul 2001 11:11:02 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: CYGWIN1.DLL Reply-to: jonadab AT bright DOT net Message-ID: <3B556EC6.21864.3DD4548@localhost> In-reply-to: <20010717233151.A12657@redhat.com> X-Eric-Conspiracy: My name is not Eric. X-Platform: Windows '95 OSR2 (heavily adjusted and customised) X-mailer: Pegasus Mail for Win32 (v3.12) # I agree 100% with most of what was written here. In fact, I think it # think it might even be nice to add it to the documentation. # # However, I do not agree that static linking is generally a # universally good idea for any platform. I was talking about Microsoft platforms specifically, because Microsoft's dynamic linking mechanism is problematic. Any platform of course may implement something (e.g., dynamic libraries) well or poorly. I also understand (or think I understand) why Cygwin uses dynamic linking, and it doesn't bother me tremendously, but it does have some implications -- which are really Microsoft's fault, but impact Cygwin nonetheless. Some of these implications come home to roost when we start talking about different people distributing different packages that are built against different versions of Cygwin. There is potential there for problems. -- Your font seems to be: proportional fixed ^ | (Fontmeter only accurate for about 90% of fonts.) -- 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/