caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Armaël Guéneau" <armael.gueneau@ens-lyon.fr>
To: caml-list@inria.fr
Subject: [Caml-list] OCamldoc plugins & ocamlbuild
Date: Fri, 18 Dec 2015 17:14:20 +0100	[thread overview]
Message-ID: <567430DC.6020009@ens-lyon.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

Hi list,

I'm wondering how one should compile ocamldoc custom generators 
<http://caml.inria.fr/pub/docs/manual-ocaml/ocamldoc.html#sec333> using
ocamlbuild.

First, the ocamlbuild manual
(https://github.com/gasche/manual-ocamlbuild/blob/master/manual.md#basic-tags-)
says that the [use_ocamldoc] tag is deprecated; and that a corresponding
ocamlfind package should be used instead. Is there such a package for 
ocamldoc?
I did not found one.

Then, I did not manage to build the plugin into .cma/.cmxs files 
directly using
ocamlbuild. My command line was something along these lines:

    ocamlbuild -use-ocamlfind -tag use_ocamldoc -package compiler-libs 
plugin.cmxs

When trying to build plugin.cma/plugin.cmxs, ocamlbuild complained that 
"Cannot
find file ocamldoc.cma/ocamldoc.cmxa" (respectively). However, I can build
plugin.cmo/plugin.cmx using the same command line, then create the 
.cma/.cmxs
manually using ocamlc/ocamlopt - which I ended up doing.

Is there a better way to do so? If the whole process can be improved 
(how?), I
would be happy to write the required patches/documentation.

— Armaël


[-- Attachment #2: Type: text/html, Size: 1749 bytes --]

             reply	other threads:[~2015-12-18 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 16:14 Armaël Guéneau [this message]
2015-12-18 17:06 ` Gabriel Scherer
2015-12-18 19:14   ` Armaël Guéneau
2015-12-18 21:43     ` Gabriel Scherer
2015-12-20 15:33       ` Armaël Guéneau

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=567430DC.6020009@ens-lyon.fr \
    --to=armael.gueneau@ens-lyon.fr \
    --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;
as well as URLs for NNTP newsgroup(s).