From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Hezekiah M. Carty" <hcarty@atmos.umd.edu>
Cc: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild .inferred.mli problem
Date: Mon, 17 Sep 2007 16:25:15 +0200 [thread overview]
Message-ID: <1190038867-sup-9845@ausone.inria.fr> (raw)
In-Reply-To: <20070916023623.GA10905@laptop44.chn.comcast.net>
Excerpts from Hezekiah M. Carty's message of Sun Sep 16 04:36:23 +0200 2007:
> I have been unable to get ocamlbuild to preprocess a single .ml file
> when creating an inferred interface file. Here is some simple code
> to illustrate the problem:
>
> test.ml:
> value f x = x + 2;
>
> _tags:
> <test.ml>: pp(camlp4r)
Using pp(...), is not the best way to use preprocessors.
Try the camlp4r tag:
"test.ml": camlp4r
[...]
> I have also tried creating a myocamlbuild.ml to get around this, but
> using something like this in myocamlbuild.ml:
>
> flag ["use_openin"]
> (S [A "-I"; A "+camlp4"; A "-pp"; A "camlp4o pa_openin.cmo"]);;
You certainly don't want to add these flags to any commands that treat a file
that is tagged use_openin. You certainly want to add them only for ocaml
preprocessing.
flag ["ocaml"; "pp"; "use_openin"]
(A"pa_openin.cmo");;
> along with a matching flag in _tags causes havoc, with each of the
> items on the list being repeated twice and quoted, leading to shell
> errors.
>
> I'm using revised syntax here as a simple example. I originally ran
> in to this issue while trying to build a library which uses the
> pa_openin camlp4 extension.
>
> Any suggestions or pointers on how to proceed with this?
HTH,
--
Nicolas Pouillard aka Ertai
next prev parent reply other threads:[~2007-09-17 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 2:36 Hezekiah M. Carty
2007-09-17 14:25 ` Nicolas Pouillard [this message]
2007-09-17 18:08 ` [Caml-list] " Hezekiah M. Carty
2007-09-18 14: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=1190038867-sup-9845@ausone.inria.fr \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=hcarty@atmos.umd.edu \
/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