delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-developers-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin-developers AT sourceware DOT cygnus DOT com |
Date: | Tue, 11 May 1999 16:19:36 -0700 |
From: | Geoffrey Noer <noer AT cygnus DOT com> |
To: | Chris Faylor <cgf AT cygnus DOT com> |
Cc: | cygwin-developers AT sourceware DOT cygnus DOT com |
Subject: | Re: -lc == -lcygwin in the next release? |
Message-ID: | <19990511161936.D31344@cygnus.com> |
References: | <19990511181107 DOT A6957 AT cygnus DOT com> |
Mime-Version: | 1.0 |
X-Mailer: | Mutt 0.95.1i |
In-Reply-To: | <19990511181107.A6957@cygnus.com>; from Chris Faylor on Tue, May 11, 1999 at 06:11:07PM -0400 |
On Tue, May 11, 1999, Chris Faylor wrote: > > Does anyone mind if I get rid of libcygwin.a in the next release > and just call it libc.a? Then when it is copied to /whatever/lib > it will work correctly when it is used on a command line. This sounds like a pretty good idea, although would it cause confusion in that libcygwin.a is more than just the contents of libc.a? (libm.a for example might still cause confusion). -- Geoffrey Noer Email: noer AT cygnus DOT com Cygnus Solutions
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |