Ok, the problem was building a dynamically linked 
library? The patch seems to work, but offer some 
slowdown.

You _can_ link drivers statically into the erlang VM,
which is how it had to be done in the olden days. 
For prototyping, this should be perfectly adequate.

Today, one normally uses erl_ddll module to dynamically 
load/unload libs, since it's much more convenient.

BR,
Ulf W

> -----Original Message-----
> From: caml-list-bounces@yquem.inria.fr 
> [mailto:caml-list-bounces@yquem.inria.fr] On Behalf Of Joel Reymont
> Sent: den 21 juni 2007 12:29
> To: Matthieu Dubuget
> Cc: caml-list@yquem.inria.fr
> Subject: Re: [Caml-list] ocaml dll in an Erlang runtime
> 
> http://tinyurl.com/yrjryv
> 
> On Jun 21, 2007, at 11:15 AM, Matthieu Dubuget wrote:
> 
> > 2007/6/21, Joel Reymont <joelr1@gmail.com>: My biggest issue with 
> > OCaml is building shared libraries.
> >
> > I tried to build a shared library for use with Ruby once and failed 
> > miserably.
> >
> > Could you please elaborate about this? Maybe not on this thread.
> 
> --
> http://topdog.cc      - EasyLanguage to C# translator
> http://wagerlabs.com  - Blog
> 
> 
> 
> 
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>