This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Re[2]: Making DLL's.
- To: Paul Sokolovsky <paul-ml@is.lg.ua>, cygwin@sourceware.cygnus.com
- Subject: Re: Re[2]: Making DLL's.
- From: jeffdbREMOVETHIS@goodnet.com (Mikey)
- Date: Tue, 23 Mar 1999 06:03:11 GMT
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- In-Reply-To: <3887.990322@is.lg.ua>
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Organization: Never
- References: <uzp55lb0a.fsf@oranda.demon.co.uk> <3887.990322@is.lg.ua>
- Reply-To: jeffdbREMOVETHIS@goodnet.com
- Sender: cygwin-owner@sourceware.cygnus.com
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 <gvaughan@oranda.demon.co.uk> 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