caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Jeremy Yallop" <jeremy.yallop@ed.ac.uk>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] building executables with camlp4
Date: Wed, 13 Jun 2007 14:23:20 +0200	[thread overview]
Message-ID: <cd67f63a0706130523wa12a391m4c3a391a390a5036@mail.gmail.com> (raw)
In-Reply-To: <466FCB46.1070304@ed.ac.uk>

On 6/13/07, Jeremy Yallop <jeremy.yallop@ed.ac.uk> wrote:
> With the 3.09 version of camlp4 I could build an executable for my
> extension by linking against various .cmx files.  Is it possible to do
> something similar with the new camlp4 in 3.10?  I've tried linking with

Yes

>
>     camlp4lib.cmxa

A good starting point

>     Camlp4Parsers/Camlp4OCamlRevisedParser.cmx
>     Camlp4Parsers/Camlp4OCamlParser.cmx
>     Camlp4Printers/Camlp4OCamlRevisedPrinter.cmx

Why not

>     Camlp4Printers/Camlp4OCamlPrinter.cmx

This is indeed useless, the real printer is in the Camlp4 package, and
Camlp4Printers/Camlp4OCamlPrinter is a dummy module to enable it.

It really depends on what you want to do, if you want to build your
own camlp4 (using Camlp4Bin) then you are in the good path (don't miss
unix, and -linkall).
If you want use camlp4 as a library and then certainly don't rely on
the Camlp4.Register module you can try camlp4fullib.cmxa.

[...]

> In case it makes things simpler I'm using OCamlMakefile,

Not specially.

-- 
Nicolas Pouillard


  reply	other threads:[~2007-06-13 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 10:47 Jeremy Yallop
2007-06-13 12:23 ` Nicolas Pouillard [this message]
2007-06-13 13:12   ` [Caml-list] " Jeremy Yallop
2007-06-13 13:27     ` Nicolas Pouillard
2007-06-13 13:27       ` Jeremy Yallop
2007-06-13 13:45         ` Nicolas Pouillard
2007-06-13 14:07           ` Jeremy Yallop

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=cd67f63a0706130523wa12a391m4c3a391a390a5036@mail.gmail.com \
    --to=nicolas.pouillard@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=jeremy.yallop@ed.ac.uk \
    /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).