From: DJ Delorie <dj@delorie.com>
To: rbresner@olf.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: How can I get a .dll to resolve at runtime ?
Date: Wed, 07 Jul 1999 15:49:00 -0000 [thread overview]
Message-ID: <199907072246.SAA07598@indy.delorie.com> (raw)
In-Reply-To: <3783C923.C7742C50@olf.com>
> Is there a way, on NT, to get a .dll to resolve externals at
> runtime, like *nix, instead of at link time?
I don't think so. What you'd normally do is have the exe call the dll
at startup and pass it pointers to its functions, which the dll would
store in per-process memory (remember that dlls are shared among many
executables).
One thing to try is to export the function with a .DEF file, and see
if that works. You'd have to build an import library for your
executable and link the dll against that, but I'm not sure if NT would
even *allow* such a hack.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: DJ Delorie <dj@delorie.com>
To: rbresner@olf.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: How can I get a .dll to resolve at runtime ?
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <199907072246.SAA07598@indy.delorie.com> (raw)
Message-ID: <19990731183400.DLIS4CubOlze41_yGEywAA4BuYzacVvFQ_jvRu6YDfk@z> (raw)
In-Reply-To: <3783C923.C7742C50@olf.com>
> Is there a way, on NT, to get a .dll to resolve externals at
> runtime, like *nix, instead of at link time?
I don't think so. What you'd normally do is have the exe call the dll
at startup and pass it pointers to its functions, which the dll would
store in per-process memory (remember that dlls are shared among many
executables).
One thing to try is to export the function with a .DEF file, and see
if that works. You'd have to build an import library for your
executable and link the dll against that, but I'm not sure if NT would
even *allow* such a hack.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-07-07 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-07 14:42 Robert Bresner
1999-07-07 15:49 ` DJ Delorie [this message]
1999-07-07 16:13 ` Tor Lillqvist
1999-07-31 18:34 ` Tor Lillqvist
1999-07-07 17:01 ` Robert Bresner
1999-07-07 17:33 ` DJ Delorie
1999-07-31 18:34 ` DJ Delorie
1999-07-31 18:34 ` Robert Bresner
1999-07-31 18:34 ` DJ Delorie
1999-07-31 18:34 ` Robert Bresner
1999-07-08 4:50 Emanuele ALIBERTI
1999-07-31 18:34 ` Emanuele ALIBERTI
1999-07-08 4:54 Emanuele ALIBERTI
1999-07-31 18:34 ` Emanuele ALIBERTI
1999-07-08 4:57 Emanuele ALIBERTI
1999-07-31 18:34 ` Emanuele ALIBERTI
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=199907072246.SAA07598@indy.delorie.com \
--to=dj@delorie.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=rbresner@olf.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).