Date: Wed, 8 Sep 1999 21:29:11 +0200
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: "Charles 'Buck' Krasic" <email@example.com>, firstname.lastname@example.org
Subject: Re: -output-obj and shared libraries?
In-Reply-To: <199909071601.JAA00745@giove.cse.ogi.edu>; from Charles 'Buck' Krasic on Tue, Sep 07, 1999 at 09:01:30AM -0700
> My target platform is Linux/x86.
> Is it possible to create a .so object from ocaml?
It depends what you want to put in the shared library and how you
want to use it.
>From your mention of the -output-obj option, I infer that you'd like
to build a shared library that contains some Caml code, some C
wrappers around the Caml code, and a copy of the Caml runtime system.
This is easy to do. Referring to the example at the end of the
"Interfacing C with Objective Caml" chapter, you'd do:
ocamlc -custom -output-obj -o modcaml.o mod.ml
ocamlc -c modwrap.c
gcc -shared -Wl,-soname,libmod.so.1 -o libmod.so.1.0 \
modwrap.o modcaml.o /usr/local/lib/ocaml/libcamlrun.a
and then install libmod.so.1.0 in a public place as usual. Then you
can dynamically link against libmod using -lmod or dlopen().
If your question is about building shared libraries of Caml code that
can be linked dynamically against other Caml code, we don't know yet
how to do this. A Caml program can load bytecode Caml object files at
run-time using the Dynlink library, but that's not quite the same
- Xavier Leroy
This archive was generated by hypermail 2b29 : Sun Jan 02 2000 - 11:58:25 MET