From: Florent Monnier <fmonnier@linux-nantes.fr.eu.org>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Toplevel - loading dependencies
Date: Fri, 9 Jan 2009 18:14:07 +0100 [thread overview]
Message-ID: <200901091814.08168.fmonnier@linux-nantes.fr.eu.org> (raw)
In-Reply-To: <49675DE7.5030000@uj.edu.pl>
> If I put everything into one big cma, then I have to recompile it every
> small change. It takes so long time, that it would make no sense to use
> the interpreter at all.
in case you're doing so this way:
ocamlc -o my.cma mod1.ml mod2.ml mod3.ml mod4.ml
this will recompile everything,
but you can use in your makefile:
%.cmo: %.ml
ocamlc.opt -c $<
my.cma: mod1.cmo mod2.cmo mod3.cmo mod4.cmo
ocamlc.opt -a -o $@ $^
then you don't recompile everything, only the modified module
if there are dependencies between modules, just add additional rules:
modfoo.cmo: modfoo.ml modbar.cmi
next prev parent reply other threads:[~2009-01-09 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 14:23 Dawid Toton
2009-01-09 14:33 ` [Caml-list] " Matthieu Dubuget
2009-01-09 17:14 ` Florent Monnier [this message]
2009-01-09 18:13 ` Dawid Toton
2009-01-09 17:53 ` Peng Zang
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=200901091814.08168.fmonnier@linux-nantes.fr.eu.org \
--to=fmonnier@linux-nantes.fr.eu.org \
--cc=caml-list@yquem.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).