caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Stefano Zacchiroli <zack@upsilon.cc>
To: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: ocamlbuild vs INCLUDE: how to copy snippets into _build/ ?
Date: Sat, 8 Nov 2008 16:09:40 +0100	[thread overview]
Message-ID: <20081108150940.GA24353@usha.takhisis.invalid> (raw)

I'm using ocamlbuild and camlp4oof to exploit the INCLUDE syntax
extension, that is have camlp4 expand in the obvious way stuff like:

  INCLUDE "some/relative/path/snippet.mli"

The path passed to INCLUDE is relative to the including file, but with
ocamlbuild I've a problem. Namely, the snippet is not copied inside
the appropriate subdir of _build, and camlp4 correctly fails with
something like:

  File "some/relative/path/snippet.mli", line 52, characters 0-3:
  I/O error: "some/relative/path/snippet.mli: No such file or directory"
  Preprocessing error on file src/foo/bar/including.mli
  Command exited with code 2.

The snippet is not otherwise processed by the OCaml toolchain, it is
just meant to be INCLUDEd.

How can I tell ocamlbuild to copy into the _build/ directory my
snippets?

My reading of the manual doesn't hint me to any useful tag ...

TIA,
Cheers.

-- 
Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è sempre /oo\ All one has to do is hit the right
uno zaino        -- A.Bergonzoni \__/ keys at the right time -- J.S.Bach


             reply	other threads:[~2008-11-08 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08 15:09 Stefano Zacchiroli [this message]
2008-11-08 15:22 ` [Caml-list] " Stéphane Glondu
2008-11-08 15:49 ` 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=20081108150940.GA24353@usha.takhisis.invalid \
    --to=zack@upsilon.cc \
    --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).