Commit 0f18e0dc authored by Pietro Abate's avatar Pietro Abate
Browse files

[r2005-08-26 15:11:46 by afrisch] Empty log message

Original author: afrisch
Date: 2005-08-26 15:11:46+00:00
parent 7c20712b
......@@ -32,38 +32,70 @@ been reused.
<box title="Download and installation" link="install">
<p>
The build procedure for OCamlDuce is exactly the same as for OCaml:
<tt>configure, make world, make install</tt>. The names of the tools
are unchanged: <tt>ocaml,ocamlc,ocamlopt</tt>. Currently, OCamlDuce
Currently, OCamlDuce
is based on OCaml 3.08.4 and on a CVS snapshots
of CDuce (between 0.3.92 and the head).
</p>
<ul>
<li><a
href="http://pauillac.inria.fr/~frisch/ocamlcduce/download/ocamlduce-3.08.4.tar.gz">Compiler,
version 3.08.4</a></li>
href="http://pauillac.inria.fr/~frisch/ocamlcduce/download/ocamlduce-3.08.4pl1.tar.gz">Compiler,
version 3.08.4, patch level 1</a></li>
</ul>
<p>
GODI users can upgrade an existing installation by adding this
There are two different installation modes:
</p>
<ul>
<li><b>Stand-alone mode</b>. OCamlDuce is used as a drop-in
replacement for OCaml. The build procedure is unchanged:
<tt>./configure &amp;&amp; make world &amp;&amp; make install</tt>.
The tools are named <tt>ocaml, ocamlc, ocamlopt</tt>, ...
The standard library is extended with the <tt>num</tt> library
and the <tt>Ocamlduce</tt> module.
</li>
<li><b>Package mode</b>. OCamlDuce is installed on top of an existing
OCaml installation (whose version number must match), without touching
it. The build
procedure is: <tt>./configure &amp;&amp; make all &amp;&amp; make opt
&amp;&amp; make install</tt>. The <tt>configure</tt> script should be called with
the same arguments as the ones used when you built OCaml. For instance,
the <tt>LIBDIR</tt> argument is used to find OCaml standard library.
The tools names are changed to <tt>ocamlduce, ocamlducec,
ocamlduceopt</tt>, ... They use the existing standard library.
In addition, a library <tt>ocamlduce.cma</tt> is built.
It depends on the <tt>nums.cma</tt> library. The <tt>install</tt>
target implements a <tt>Findlib</tt>-based installation. It registers
a package named <tt>ocamlduce</tt> and it puts the tools
in the package sub-directory (the <tt>BINDIR</tt> and <tt>LIBDIR</tt>
arguments to <tt>configure</tt> are not used). The toplevel
can be called by <tt>ocamlfind ocamlduce/ocamlduce</tt>.
</li>
</ul>
<p>
GODI users can choose any of these two modes.
In order to upgrade an existing installation so as to use
OCamlDuce in place of OCaml, they must add this
line to their <tt>etc/godi.conf</tt> file:
</p>
<sample>
GODI_BUILD_SITES += http://pauillac.inria.fr/~frisch/ocamlcduce/godi
</sample>
<p>
and by forcing a recompilation of the <tt>godi-ocaml-src</tt>
and <tt>godi-ocaml</tt> packages. <!--They should also build
the <tt>godi-xml-support</tt> library.-->
and force a recompilation of the <tt>godi-ocaml-src</tt>
and <tt>godi-ocaml</tt> packages. The alternative is to install OCamlDuce
as a GODI package over an existing installation. You don't need
to touch the <tt>etc/godi.conf</tt> file. The package
name is <tt>godi-ocamlduce</tt>. In order to use the new compilers
and tools, you can make the environment variable
<tt>OCAMLFIND_CONF</tt> point to the
<tt>$GODI/etc/findlib-ocamlduce.conf</tt> file and then
uses e.g. <tt>ocamlfind ocamlc -package ocamlduce</tt>.
</p>
<!--
<p>
Some simple examples can be found <a -->
<!--href="http://pauillac.inria.fr/~frisch/ocamlcduce/tests/">here</a>.</p>
-->
</box>
<box title="Overview" link="overview">
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment