Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Josh Berdine" <berdine@dcs.qmul.ac.uk>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamlbuild: caching and -dtypes
Date: Wed, 2 May 2007 09:21:35 +0200	[thread overview]
Message-ID: <cd67f63a0705020021i3e4d35d2r9a5bda858e412288@mail.gmail.com> (raw)
In-Reply-To: <00c901c78c3f$5bda4d10$138ee730$@qmul.ac.uk>

On 5/2/07, Josh Berdine <berdine@dcs.qmul.ac.uk> wrote:
> Hi,
Hello,

> 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.

When no source is modified the second run shouldn't trigger any
command. In my tests I use the -nothing-should-be-rebuilt option to
ensure it. If you find a counter example of reasonably sized I'll dig
a little to see what's wrong.

> Also, has anyone trained tuareg to look for .annot files in the build
> directory, or else taught ocamlbuild to put the .annot files back?

That's a known issue, the tuareg mode will be upgraded soon.

Regards,

-- 
Nicolas Pouillard


      reply	other threads:[~2007-05-02  7:21 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
2007-05-02  7:21   ` Nicolas Pouillard [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=cd67f63a0705020021i3e4d35d2r9a5bda858e412288@mail.gmail.com \
    --to=nicolas.pouillard@gmail.com \
    --cc=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