From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Joel Reymont" <joelr1@gmail.com>
Cc: "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild, camlp4 and the _tags file
Date: Mon, 30 Apr 2007 14:01:40 +0200 [thread overview]
Message-ID: <cd67f63a0704300501m685cd30ci7c6ff7018220c7e4@mail.gmail.com> (raw)
In-Reply-To: <D201DC4F-A217-4ABC-A229-039940FF8321@gmail.com>
On 4/30/07, Joel Reymont <joelr1@gmail.com> wrote:
> I see that ocamlbuild is being used to build camlp4 examples.
>
> I thought I would ask a few questions on the meaning of the different
> tags since they are not described in my version of the ocamlbuild
> user's guide and the presentation slides.
>
> >>> "apply_operator.ml" or "type_quotation.ml": camlp4rf, use_camlp4
>
> The above is clear.
>
> >>> "lambda_quot.ml": camlp4rf, use_camlp4_full
>
> But what's the difference between use_camlp4_full and use_camlp4?
use_camlp4_full put a dependency on camlp4fulllib.{cma,cmxa}.
The camlp4fullib contains all the camlp4 modules including parsers,
printers... Some modules are incompatible and then loading them
together is only useful when using camlp4 as a library.
> When should one be used vs the other?
use_camlp4_lib most of the time.
> >>> "test_macros.ml": pp(camlp4of ./macros.cmo)
> >>> "lambda_test.ml": pp(camlp4of ./lambda_quot.cmo)
>
> Why are these special options needed? When should I use them?
That's just examples, here macros.cmo and lambda_quot.cmo are camlp4
extensions.
In your case you can do something like.
"foo.ml": pp(camlp4o -filter map -filter fold)
> >>> <parse_files.*>: camlp4of, use_camlp4_full, use_dynlink
>
> Why is dynlink used here?
Since camlp4 use dynlink one needs it too in order to link a standalone program.
--
Nicolas Pouillard
prev parent reply other threads:[~2007-04-30 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 11:30 Joel Reymont
2007-04-30 12:01 ` Nicolas Pouillard [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=cd67f63a0704300501m685cd30ci7c6ff7018220c7e4@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=joelr1@gmail.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