From 71a670e63e80b62ff42bb18b8a73bfb64984684e Mon Sep 17 00:00:00 2001
From: Sylvain Le Gall <sylvain.le-gall@polytechnique.org>
Date: Mon, 27 Oct 2003 20:51:43 +0000
Subject: [PATCH] Still writing Sylvain LE GALL

---
 chapter-liblocal.xml | 34 +++++++++++++++++++++++++++++++---
 chapter-ocaml.xml    | 31 ++++++++++++++++++++++++++++++-
 2 files changed, 61 insertions(+), 4 deletions(-)

diff --git a/chapter-liblocal.xml b/chapter-liblocal.xml
index ddad9a85..0fe2b9b5 100644
--- a/chapter-liblocal.xml
+++ b/chapter-liblocal.xml
@@ -1,3 +1,31 @@
-   <section id="liblocal-camlp4">
-    <title>Camlp4 files</title>
-   </section>
+    <para>
+    Installation and use of locally installed &ocaml-name; is out of the 
+    scope of this document. However, in order to have it work with a standard
+    &ocaml-name; &debian-name; install, you should follow some guideline.
+    </para>
+
+    <section id="liblocal-path">     
+    <para>You user this path to install local library and executable :
+    <variablelist>
+     <varlistentry>
+      <term>bytecoded executable</term>
+      <listitem>/usr/local/bin</listitem>
+      <listitem>/usr/local/sbin</listitem>
+     </varlistentry>
+     <varlistentry>
+      <term>bytecoded library ( <filename>*.cma</filename> )</term>
+      <listitem>/usr/local/lib/ocaml/&ocaml-version;/
+      <listitem>native executable</listitem>
+      <listitem>native library ( <filename>*.cmxa</filename> )</listitem>
+      <listitem>shared library ( for C-binding ) ( <filename>dll*.so</filename> )</listitem>
+      <listitem>static library ( for C-binding ) ( <filename>lib*.a</filename> )</listitem>
+      <listitem>bytecoded object ( <filename>*.cmo</filename> )</listitem>
+      <listitem>native object ( <filename>*.cmx</filename> )</listitem>
+      <listitem>configuration file for handling library ( <filename>META</filename> )</listitem>
+      <listitem>&ocamldoc; generated documentation ( <filename>*.odoc</filename> )</listitem>
+      <listitem>&camlp4; related files ( <filename>*.cm[ao]</filename> )</listitem>
+     </simplelist>
+    </para>
+
+
+    </section>
diff --git a/chapter-ocaml.xml b/chapter-ocaml.xml
index ad57135a..2afcfc8f 100644
--- a/chapter-ocaml.xml
+++ b/chapter-ocaml.xml
@@ -46,6 +46,7 @@
       <listitem>native object ( <filename>*.cmx</filename> )</listitem>
       <listitem>configuration file for handling library ( <filename>META</filename> )</listitem>
       <listitem>&ocamldoc; generated documentation ( <filename>*.odoc</filename> )</listitem>
+      <listitem>&camlp4; related files ( <filename>*.cm[ao]</filename> )</listitem>
      </simplelist>
     </para>
    
@@ -270,8 +271,36 @@
    author to have a well commented source.
    </para>
    </subsection>
-   
 
+   <subsection id="camlp4-path">
+   <para>
+   Actually, &camlp4; extensions are stored in 
+   <filename>/usr/lib/ocaml/&ocaml-version;/camlp4/</filename>. In order to do something
+   cleaner, &ocaml-force; propose to put this files in their own directory, even in their
+   own package. It is not mandatory, but it could ease a lot, the user of camlp4, by avoiding
+   name clash.
+   </para>
+
+   <para>
+   You just have to consider &camlp4; file just as standard library, except that you
+   prefix them with <varname>-syntax</varname>. <example>For example : the syntax 
+   extension coming with <application>libokey-ocaml-dev</application> should be stored
+   in <filename>/usr/lib/ocaml/&ocaml-version;/okey-syntax/</filename>, the package
+   containing it should be called <application>libokey-syntax-ocaml-dev</application>.
+   </example>
+   </para>
+
+   <para>
+   It is recommended to use <filename>META</filename> to specify how to handle this
+   extension.
+   </para>
+
+   <para>
+   All definition is taken from previous text considering syntax extension as a standalone
+   library.
+   </para>
+
+   </subsection>
    </section>
 
 
-- 
2.30.2