caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nicolas Cannasse" <warplayer@free.fr>
To: "Xavier Leroy" <xavier.leroy@inria.fr>, "Chris Hecker" <checker@d6.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlc linking loads dlls?
Date: Thu, 14 Nov 2002 20:16:15 -0000	[thread overview]
Message-ID: <009301c28c12$4dcee5a0$3c00a8c0@warp> (raw)
In-Reply-To: <20021114160348.B9597@pauillac.inria.fr>

> > Why does ocamlc load dlls during linking?
>
> Just to make sure that all external C functions referenced from your
> Caml code are indeed defined in the DLLs you provide.  Otherwise, the
> error would only be detected at run time, and earlier is better.
>
> > a) dlls that aren't in the path during build, and
> > b) dlls that do complex stuff in their dllmain.
>
> I agree b) is a bit of a problem, but I don't know of any portable way
> to test whether DLL x.dll defines symbol "foo" than to link x.dll and
> query the address of "foo".

That point can be resolved by calling LoadLibraryEx with the
DONT_RESOLVE_DLL_REFERENCE flag.
According to MS docs, this prevent the call of DllMain.

Nicolas Cannasse

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2002-11-14 19:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14  6:25 Chris Hecker
2002-11-14 15:03 ` Xavier Leroy
2002-11-14 18:21   ` Chris Hecker
2002-11-14 20:16   ` Nicolas Cannasse [this message]
2002-11-14 19:21     ` Chris Hecker
2002-11-15  0:55       ` Jacques Garrigue
2002-11-15  1:53         ` Gerd Stolpmann
2002-11-15  6:59         ` Chris Hecker
2002-11-15  7:07           ` Jacques Garrigue
2002-11-15  8:00             ` Chris Hecker

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='009301c28c12$4dcee5a0$3c00a8c0@warp' \
    --to=warplayer@free.fr \
    --cc=caml-list@inria.fr \
    --cc=checker@d6.com \
    --cc=xavier.leroy@inria.fr \
    /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 NNTP newsgroup(s).