caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dario Teixeira <darioteixeira@yahoo.com>
To: DooMeeR <d@doomeer.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ocamlbuild + Ocamldoc troubles
Date: Tue, 4 Nov 2008 12:49:08 -0800 (PST)	[thread overview]
Message-ID: <391288.35718.qm@web54604.mail.re2.yahoo.com> (raw)
In-Reply-To: <4910AE01.3090504@doomeer.com>

Hi,

> So, ocamldoc doesn't find "intro.txt". This is because this
> file is not copied into the _build directory by ocamlbuild.
> You need to explain to ocamlbuild, in your plugin, that your
> target (lambdoc.docdir/index.html) depends on "intro.txt",
> otherwise ocamlbuild won't copy the file. Even if you copy
> the file yourself into the _build directory,  ocamlbuild
> might delete it.
>
> If I remember correctly there is a function of the plugin
> API, called "dep" if I'm not mistaken, which does exactly
> this.

Thanks for the reply.  Ideally one should be able to specify
that info in the _tags file and/or with other special files.
And I reckon that Ocamlbuild probably already supports that.

By the way, I have managed to get Ocamlbuild to invoke Ocamldoc
for the source code files only (no intro or tutorials) by
creating a lambdoc.odocl file whose contents are the same as
lambdoc.mlpack's.  However, the compilation fails with a
mysterious "analyse_module: parsetree and typedtree don't match"
error:

+ ocamlfind ocamldoc -dump lambdoc/document_ast.odoc -package extlib -package ocsigen.xhtml -package pcre -package sexplib -package threads -package unix -package xml-light -I lambdoc -I lambdoc/readers -I lambdoc/writers -I lambdoc/readers/lambtex_reader_impl lambdoc/document_ast.ml
analyse_module: parsetree and typedtree don't match.
1 error(s) encountered
Command exited with code 1.

Any ideas?

Cheers,
Dario






      reply	other threads:[~2008-11-04 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 19:19 Dario Teixeira
2008-11-04 20:18 ` [Caml-list] " DooMeeR
2008-11-04 20:49   ` Dario Teixeira [this message]

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=391288.35718.qm@web54604.mail.re2.yahoo.com \
    --to=darioteixeira@yahoo.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=d@doomeer.com \
    /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;
as well as URLs for NNTP newsgroup(s).