From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"Anders Peter Fugmann" <anders@fugmann.net>,
caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Speeding up compilation
Date: Wed, 2 Apr 2014 16:54:12 -0400 [thread overview]
Message-ID: <CAN6ygO=c4zUcP7iqZjWOB533_LLA=gGF-sZee52M6zLhnPCeoA@mail.gmail.com> (raw)
In-Reply-To: <CAHvkLrNyM-gkG+dOpjhktJpgOPP8nsSzRL3Ldr9b36zQzbyX3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
I've had good experience shifting from a custom makefile to using
ocamlbuild on a project with around 120 files and moderate preprocessing.
The custom makefile was a pain to maintain and seemed to be doing too much
work.
-Yotam
On Wed, Apr 2, 2014 at 4:43 PM, Fabrice Le Fessant <
Fabrice.Le_fessant@inria.fr> wrote:
> ocp-build uses a trick to speed-up compilations with camlp4: it
> preprocesses every file only once, and then uses the generated file (a
> binary version of the file AST) with ocamldep, ocamlc and ocamlopt. It
> usually means a x3 speedup.
>
> --Fabrice
>
>
> On Wed, Apr 2, 2014 at 10:34 PM, Daniel Bünzli <
> daniel.buenzli@erratique.ch> wrote:
>
>>
>>
>> Le mercredi, 2 avril 2014 à 22:14, Anders Peter Fugmann a écrit :
>>
>> > Is there any way to use a optimized version of camlp4.
>>
>> Not sure that this will work as it it not mentioned in the documentation
>> [1] but did you try to add
>>
>> camlp4="camlp4.opt"
>>
>> in .opam/$SWITCH/lib/findlib.conf (or wherever it is on your machine).
>>
>> Best,
>>
>> Daniel
>>
>> [1]
>> http://projects.camlcity.org/projects/dl/findlib-1.4.1/doc/ref-html/r775.html
>>
>>
>>
>> --
>> 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
>>
>
>
>
> --
> Fabrice LE FESSANT
> Chercheur en Informatique
> INRIA Paris Rocquencourt -- OCamlPro
> Programming Languages and Distributed Systems
>
[-- Attachment #2: Type: text/html, Size: 2735 bytes --]
next prev parent reply other threads:[~2014-04-02 20:54 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 [this message]
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
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='CAN6ygO=c4zUcP7iqZjWOB533_LLA=gGF-sZee52M6zLhnPCeoA@mail.gmail.com' \
--to=yotambarnoy@gmail.com \
--cc=Fabrice.Le_fessant@inria.fr \
--cc=anders@fugmann.net \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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).