From: "François Pottier" <francois.pottier@inria.fr>
To: caml-list@inria.fr
Cc: github@mjambon.com, Gabriel Scherer <gabriel.scherer@gmail.com>
Subject: [Caml-list] cppo, ocamlbuild, and dependencies
Date: Tue, 31 Jan 2017 22:50:10 +0100 [thread overview]
Message-ID: <58910692.1060706@inria.fr> (raw)
Dear OCaml users,
I am trying to use cppo and ocamlbuild together.
Suppose the file a.cppo.ml contains the line:
#include "b.cppo.ml".
Then, the build fails. As far as I understand, ocamlbuild is not aware
of the
dependency a.cppo.ml -> b.cppo.ml, so the source file b.cppo.ml is not even
copied to the _build directory.
I am using the build rules bundled with cppo (in the module
Ocamlbuild_cppo).
Shouldn't these build rules be improved so as to perform a genuine
dependency
computation? Has anyone run into this issue?
Thanks,
--
François Pottier
francois.pottier@inria.fr
http://gallium.inria.fr/~fpottier/
next reply other threads:[~2017-01-31 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 21:50 François Pottier [this message]
2017-02-01 10:19 ` Gabriel Scherer
2017-02-01 13:40 ` François Pottier
2017-02-01 17:10 ` Gabriel Scherer
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=58910692.1060706@inria.fr \
--to=francois.pottier@inria.fr \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=github@mjambon.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