From: Romain Bardou <Romain.Bardou@lri.fr>
To: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] ocamlbuild rules generating multiple files
Date: Wed, 11 Feb 2009 12:48:24 +0100 [thread overview]
Message-ID: <4992BB08.8060309@lri.fr> (raw)
In-Reply-To: <D7E06A96-39D7-429E-89A1-E3A4A7AC20F5@erratique.ch>
Daniel Bünzli a écrit :
> Hello,
>
> If in a rule a command generates multiple files (which don't necessary
> have the same basename as the dep), how can I make ocamlbuild understand
> that these files now exist in _build ?
I also encountered this problem, and AFAIK there is no support yet for
what I would call "dynamic productions". The answer of Nicolas Pouillard
was: "hmm good question... indeed it should be added" (roughly
translated :) ).
--
Romain Bardou
prev parent reply other threads:[~2009-02-11 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 22:15 Daniel Bünzli
2009-02-10 22:33 ` [Caml-list] " Hezekiah M. Carty
2009-02-10 22:39 ` Daniel Bünzli
2009-02-10 22:51 ` Hezekiah M. Carty
2009-02-10 22:59 ` Mikkel Fahnøe Jørgensen
2009-02-11 11:48 ` Romain Bardou [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=4992BB08.8060309@lri.fr \
--to=romain.bardou@lri.fr \
--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).