From: Jeremy Yallop <jeremy.yallop@ed.ac.uk>
To: caml-list@inria.fr
Subject: building executables with camlp4
Date: Wed, 13 Jun 2007 11:47:34 +0100 [thread overview]
Message-ID: <466FCB46.1070304@ed.ac.uk> (raw)
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
camlp4lib.cmxa
Camlp4Parsers/Camlp4OCamlRevisedParser.cmx
Camlp4Parsers/Camlp4OCamlParser.cmx
Camlp4Printers/Camlp4OCamlRevisedPrinter.cmx
Camlp4Printers/Camlp4OCamlPrinter.cmx
which results in an executable that fails with Not_found when run,
apparently due to a failure to delete a rule from the grammar. Building
a set of bytecode (.cmo) files and loading them with camlp4o works as
expected.
In case it makes things simpler I'm using OCamlMakefile,
Jeremy.
next reply other threads:[~2007-06-13 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 10:47 Jeremy Yallop [this message]
2007-06-13 12:23 ` [Caml-list] " Nicolas Pouillard
2007-06-13 13:12 ` 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=466FCB46.1070304@ed.ac.uk \
--to=jeremy.yallop@ed.ac.uk \
--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).