From: Pietro Abate <Pietro.Abate@pps.univ-paris-diderot.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Speeding up compilation
Date: Tue, 8 Apr 2014 19:32:23 +0200 [thread overview]
Message-ID: <20140408173223.GA26883@zed.irill.org> (raw)
In-Reply-To: <533C6FC2.9080406@fugmann.net>
For quite a while I've simply used
pp(camlp4o.opt -I_build Camlp4MacroParser.cmxs)
in my _tag file and make sure that the plugin
Camlp4MacroParser.cmxs was either available on that I made
available in the _build directory.
In my makefile I have a rule I use to compile the plugin
before calling ocamlbuild. If you use a configure script
you can change accordingly these elements to use camlp4o instead
of camlp4o.opt .
camlp4cmxs:
mkdir -p _build
ocamlopt -shared $(shell ocamlc -where)/camlp4/Camlp4Parsers/Camlp4MacroParser.cmx -o _build/Camlp4MacroParser.cmxs
p
On 02/04/14 22:14, Anders Peter Fugmann wrote:
> Hi,
>
> While trying to speed up compilation of a project of around ~150 source
> files, i found that ocamlfind invokes a bytecode version of CamlP4.
>
> Our homemade Makefile uses ocamlfind to compile bytecode and optimized code
> as well as dependency tracking using ocamldep and hand written tools. Almost
> every source file makes use of p4 extensions.
>
> When compiling though ocamlfind using the -syntax flag, I can see that
> ocamlfind starts ocamlp4 which is ocaml bytecode, and I cannot find any
> flags that allows me to use any optimized version. Also it seems that an
> optimized version of camlp4 is compiled (ocaml compiler is compiled via
> opam).
>
> Is there any way to use a optimized version of camlp4. Also any other ideas
> on how to speed up compilation would be appreciated.
>
> Regards
> Anders Fugmann
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
prev parent reply other threads:[~2014-04-08 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 20:14 Anders Peter Fugmann
2014-04-02 20:34 ` Daniel Bünzli
2014-04-02 20:43 ` Fabrice Le Fessant
2014-04-02 20:54 ` Yotam Barnoy
2014-04-03 2:10 ` Francois Berenger
2014-04-02 21:00 ` Anders Peter Fugmann
2014-04-02 20:49 ` Anders Peter Fugmann
2014-04-02 21:09 ` Daniel Bünzli
2014-04-02 21:42 ` Gerd Stolpmann
2014-04-03 21:00 ` Anders Peter Fugmann
2014-04-04 20:55 ` Gerd Stolpmann
2014-04-08 17:32 ` Pietro Abate [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=20140408173223.GA26883@zed.irill.org \
--to=pietro.abate@pps.univ-paris-diderot.fr \
--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