public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Paul Sokolovsky <paul-ml@is.lg.ua>
To: Mikey <jeffdbREMOVETHIS@goodnet.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re[4]: Making DLL's.
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <14601.990324@is.lg.ua> (raw)
Message-ID: <19990331194500.MxFyj2qOR7SZBVnmpGnL1yAvK_CN9GS5L3lmzPExf2Y@z> (raw)
In-Reply-To: <36f7285a.77752976@mail.goodnet.com>

Hello Mikey,

Mikey <jeffdbREMOVETHIS@goodnet.com> wrote:

M> Who told you this, or how did you test it?
M> all you need to do for mutually dependant
M> .dll's is to create an implib from a .def file
M> before linking. see the msdn.

   I tried to split large dll in two smaller, I build them but none of
them could be loaded. I just have tried make it with clean trivial
example and it works, so that probably was other (mine) bug. Problem
is that windoze doesn't explain clearly where's error - it doesn't
load at all with that stupid status 'A device attached to the system
is not functioning' %) . By the way, testing that, I found that
dlltool doesn't want to export one-character symbols %)

M> On Mon, 22 Mar 1999 21:17:24 +0200, you wrote:

>>
>>     To add more confusion (though maybe it not really matters in
>>practise), dlls can't be mutually dependent (tested on win95)
>>

Best regards,
 Paul                            mailto:paul-ml@is.lg.ua


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  parent reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-18 13:07 Serguei DACHIAN
1999-03-19  3:30 ` Paul Sokolovsky
1999-03-19  6:01   ` Sebastien Carpe
     [not found]     ` < 36F258AB.CC1A1788@atos-group.com >
1999-03-19  7:30       ` DJ Delorie
1999-03-22  2:32         ` Gary V. Vaughan
1999-03-22  7:28           ` John Mullee
1999-03-22  8:56             ` Gary V. Vaughan
1999-03-22 11:15               ` Re[2]: " Paul Sokolovsky
     [not found]                 ` < 3887.990322@is.lg.ua >
1999-03-22 22:25                   ` Mikey
1999-03-23  2:32                     ` Gary V. Vaughan
1999-03-31 19:45                       ` Gary V. Vaughan
1999-03-24  4:35                     ` Paul Sokolovsky [this message]
1999-03-31 19:45                       ` Re[4]: " Paul Sokolovsky
1999-03-31 19:45                     ` Re[2]: " Mikey
1999-03-23  1:13                 ` Gary V. Vaughan
1999-03-31 19:45                   ` Gary V. Vaughan
1999-03-31 19:45                 ` Paul Sokolovsky
1999-03-31 19:45               ` Gary V. Vaughan
1999-03-31 19:45             ` John Mullee
     [not found]           ` < u1zihvmrf.fsf@oranda.demon.co.uk >
1999-03-22 14:50             ` Fergus Henderson
1999-03-23  1:47               ` Gary V. Vaughan
1999-03-31 19:45                 ` Gary V. Vaughan
1999-03-31 19:45               ` Fergus Henderson
1999-03-31 19:45           ` Gary V. Vaughan
1999-03-31 19:45         ` DJ Delorie
1999-03-31 19:45     ` Sebastien Carpe
1999-03-31 19:45   ` Paul Sokolovsky
1999-03-31 19:45 ` Serguei DACHIAN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14601.990324@is.lg.ua \
    --to=paul-ml@is.lg.ua \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=jeffdbREMOVETHIS@goodnet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).