From: "Josh Berdine" <berdine@dcs.qmul.ac.uk>
To: <caml-list@yquem.inria.fr>
Subject: ocamlbuild: caching and -dtypes
Date: Tue, 1 May 2007 23:23:29 +0100 [thread overview]
Message-ID: <00c901c78c3f$5bda4d10$138ee730$@qmul.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Hi,
I've been trying out ocamlbuild, very cool indeed, thanks!
But I wonder, am I the only one who is experiencing ocamlbuild caching fewer
generated files than I would expect? I haven't had time to investigate
fully, but when building native code I see something like only two thirds of
the files being cached from one successful build to the next when no sources
are modified.
Also, has anyone trained tuareg to look for .annot files in the build
directory, or else taught ocamlbuild to put the .annot files back?
Cheers, Josh
[-- Attachment #2: Type: text/html, Size: 4810 bytes --]
next reply other threads:[~2007-05-01 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AceMP1ZZ1pZbLGIbTl+rWi5PDgef1w==>
2007-05-01 22:23 ` Josh Berdine [this message]
2007-05-02 7:21 ` [Caml-list] " Nicolas Pouillard
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='00c901c78c3f$5bda4d10$138ee730$@qmul.ac.uk' \
--to=berdine@dcs.qmul.ac.uk \
--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).