Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 19 Oct 2003 11:16:08 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Patch for building libcrypt.a as a DLL Message-ID: <20031019091608.GC25076@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3F91AED7.2010504@cwilson.fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F91AED7.2010504@cwilson.fastmail.fm> User-Agent: Mutt/1.4.1i On Sat, Oct 18, 2003 at 05:21:27PM -0400, Charles Wilson wrote: > This should make life a little simpler for those apps that use libtool > to build DLLs and depend on libcrypt -- since libtool tries very hard to > ensure that all dependencies of a DLL are themselves DLLs. > > Corinna, please consider this patch. Sure, thanks for the patch. I've changed the Makefile a bit, using `install -d' instead of the `if [ -d ...' expressions and adding the installation of a crypt.README file. Just one question: Does an additional libcrypt.la file make sense? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/