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: <39AEE158.DB923296@ece.gatech.edu> Date: Thu, 31 Aug 2000 18:51:04 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Collins CC: cygwin@sources.redhat.com Subject: Re: DLL naming conventions References: <20000831194146.867.qmail@web120.yahoomail.com> <20000831154242.B7880@cygnus.com> <39AEC3AD.42FE1CB9@ece.gatech.edu> <20000831171339.A15393@cygnus.com> <39AEDDC9.D4315497@ece.gatech.edu> <00ee01c0139e$3a7572b0$f7c723cb@lifelesswks> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Robert Collins wrote: > > I'll probably get shouted at for this but... > what about using dcom for shared libraries? It's designed to handle > versioning issues transparently, load the library from whatever location > desired etc. No, not shouted at. I don't think cygwin-binutils can do "Distributed COM (TM microsoft, copyright microsoft blah blah" builds, though, so it's not really applicable to this discussion. Unless you want to add Distributed COM support to ld? ("Distributed COM" a.k.a. COM+ a.k.a. .NET a.k.a Microsoft's-next-marketing-brainstorm is what you mean by 'dcom', right?) --Chuck -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com