From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: Benedikt Grundmann <benedikt-grundmann@web.de>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild -pack and ocamldoc
Date: Wed, 28 Nov 2007 14:11:27 +0100 [thread overview]
Message-ID: <1196255261-sup-5716@port-ext2.ensta.fr> (raw)
In-Reply-To: <9b415f950711280311j1a6ceaf0ldc8191ccd6478d4b@mail.gmail.com>
Excerpts from Benedikt Grundmann's message of Wed Nov 28 12:11:02 +0100 2007:
> Hi list (and Nicolas in particular),
Hi,
> I have a rather big project consisting of several parts. I currently
> build everything
> using one central myocamlbuild.ml file, one pN.mlpack file for each
> part, a _tags file in each part that adds the for-pack(pN) option and
> sometimes the necessary camlp4o, use_<syntaxext> tag.
> The parts are not independent of each other.
Sounds good.
> I want to add a (ocamldoc) reference to my project. Ideally one for
> the complete project, where each part is correctly packed and there is
> one central index.html file. Originally I had a file pN/pNdoc.odocl
> for each part pN and called ocamlbuild pN/pNdoc.docdir/index.html,
> which worked until I added the -pack option. Now depending on the
> options I set, I either get an error message by ocamlbuild stating
> that it does not know how to build pN/foo.odoc or an error message by
> ocamldoc stating that it does not know how to find certain files.
>
> What is the proper way to use ocamldoc together with ocamlbuild in
> such a scenario?
There is no proper way, but a way that works quite well. You can define a
rule that syntacly pack all your interfaces into a big mli. Then give it to
ocamldoc.
--
Nicolas Pouillard aka Ertai
next prev parent reply other threads:[~2007-11-28 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 11:11 Benedikt Grundmann
2007-11-28 13:11 ` Nicolas Pouillard [this message]
2007-11-28 14:22 ` [Caml-list] " Ashish Agarwal
2007-11-28 18:26 ` Nicolas Pouillard
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=1196255261-sup-5716@port-ext2.ensta.fr \
--to=nicolas.pouillard@gmail.com \
--cc=benedikt-grundmann@web.de \
--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