Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <39B3A2EC.92CFC48F@vinschen.de> Date: Mon, 04 Sep 2000 15:26:04 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Robert Collins CC: cygwin@sources.redhat.com Subject: Re: DLL naming conventions References: <17B78BDF120BD411B70100500422FC6309E0C3@IIS000> <001b01c0166d$d8f49d90$f7c723cb@lifelesswks> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Robert Collins wrote: > Personally I think that a mingw32 libpng should be useable by cygwin gcc AND > cygwin distributed binaries, given that they are the same version... (and > that should be part of the naming convention). How do you want to overcome the problems in using common stuff, say, stdio? Libraries do use other libraries. Many libraries are depending on libc calls for example. If you compile your lib for Mingw32 use, your library will require msvcrt library for stdio stuff while the same library compiled for Cygwin requires cygwin1 for the same functions. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@sources.redhat.com Red Hat, Inc. mailto:vinschen@cygnus.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com