caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jeff Henrikson" <jehenrik@yahoo.com>
To: <caml-list@inria.fr>
Subject: [Caml-list] dlopen win32 port
Date: Fri, 31 Aug 2001 18:00:01 -0400	[thread overview]
Message-ID: <000401c13268$48473ba0$0b01a8c0@mit.edu> (raw)

Hi caml-list,

I made the "dlopen" ocaml library compile under win32.  I don't have any idea how to integrate changes into the autotools scripts,
or if it is worth it to do so.  Opinions?

Win32 has functions that correspond nearly one to one with dlopen dlsym and dlclose.  The only compatability issue I can think of
are windows' fairly uniform use of stdcall for DLL functions, and the corresponding name mangling of foo(int x, int y) to _foo@4.
It seems like there should be some wrapping around this to make it disappear so that equal C files link the same on both platforms.
Would need to have a switch to turn it off for dlls that break the convention.  Haven't done that yet.

I have been trying to get a Mac port of this, but I am too much of newbie at MPW right now.  But I from what I've read I think
think the CFM model for dynamic linking is a bit more exotic.

Does anybody have a bulletproof way to unzip source code on Mac?  I used the obvious stuffit expander to unsit the ocaml source,
and after various control panel tweaking (Stuffit by default thinks Makefile.Mac is a picture for some reason) I still get CRLF
problems with :tools:make-opcodes.Mac.  There are at least two other build problems that I have used duct tape to fix.  (I'm using
the 3.02 tarball right now, the 3.01 mac makefiles had more errors)

Is it me or does the DoMake script have to start from scratch every time you make it?

> Xavier Leroy wrote on 8/24:
>"dynamic_loading" branch on the OCaml development sources
>(camlcvs.inria.fr).  I'll post more information about it once I'm
>happy with the result, to get some feedback on the design.

I checked out these sources and did some superficial diffing of it, and it wasn't obvious to me which the salient changes were.  I
think I was diffing source that was too old though (3.01).  A big mess.  Is this code for dynamic linking FFI code like DlOpen, or
for the general problem of incorporating typing info and etc from one Caml module into another at runtime?


Jeff Henrikson



-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


             reply	other threads:[~2001-08-31 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31 22:00 Jeff Henrikson [this message]
2001-09-01 10:06 ` Xavier Leroy
2001-09-01 18:47   ` [Caml-list] dynamic linking ocamlopt? Jeff Henrikson

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='000401c13268$48473ba0$0b01a8c0@mit.edu' \
    --to=jehenrik@yahoo.com \
    --cc=caml-list@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).