Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: jeffdbREMOVETHIS@goodnet.com (Mikey) To: Paul Sokolovsky , cygwin@sourceware.cygnus.com Subject: Re: Re[2]: Making DLL's. Date: Tue, 23 Mar 1999 06:03:11 GMT Organization: Never Reply-To: jeffdbREMOVETHIS@goodnet.com Message-ID: <36f7285a.77752976@mail.goodnet.com> References: <3887.990322@is.lg.ua> In-Reply-To: <3887.990322@is.lg.ua> X-Mailer: Forte Agent 1.5/32.452 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Who told you this, or how did you test it? all you need to do for mutually dependant .dll's is to create an implib from a .def file before linking. see the msdn. On Mon, 22 Mar 1999 21:17:24 +0200, you wrote: >Hello Gary, > >Gary V. Vaughan wrote: > >[] > >GVV> Is there a better solution to this than trying to find out the complete list >GVV> of libraries (and their types) against which each object will eventually be >GVV> linked so that I can tag data exports correctly when the asm code is >GVV> generated? > > To add more confusion (though maybe it not really matters in >practise), dlls can't be mutually dependent (tested on win95) > >GVV> Cheers, >GVV> Gary. > > >Best regards, > Paul mailto:paul-ml@is.lg.ua -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com