caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Hezekiah M. Carty" <hcarty@atmos.umd.edu>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] ocamlbuild rules generating multiple files
Date: Tue, 10 Feb 2009 17:51:21 -0500	[thread overview]
Message-ID: <3a360f590902101451m41eff2efx42de4cde14f0058d@mail.gmail.com> (raw)
In-Reply-To: <CCD807BD-A9DC-4AC4-95EB-580A73047727@erratique.ch>

On Tue, Feb 10, 2009 at 5:39 PM, Daniel Bünzli
<daniel.buenzli@erratique.ch> wrote:
>
> Le 10 févr. 09 à 23:33, Hezekiah M. Carty a écrit :
>
>> I've used the following rule under After_rules in myocamlbuild.ml for
>
> [...]
>
> Thanks but my problem is that the generated file do not have the same
> basename as the dep i.e. I cannot specify the ~prods arg, the ~prods are
> going to be discovered while the rule is executed and without going through
> further "build" argument invocations.
>
> Maybe a good example is tar archives. Let's say I have a rule that takes a
> .tgz and produces its files. How do I tell ocamlbuild that these files now
> exist.

Ah, my apologies.  I didn't read your original post carefully enough.
Would it be possible to write a function to read these files in to a
list then use "dep [foo; bar] file_list;"?  This is what I use for
included files in .idl files.  I have only done this with static,
pre-defined lists using 'dep ["compile"; "camlidl"] ["file1.inc;
file2.inc"];'.  I'm not sure how well it would work or if it would
work at all with a dynamic list of files.

Hez

-- 
Hezekiah M. Carty
Graduate Research Assistant
University of Maryland
Department of Atmospheric and Oceanic Science


  reply	other threads:[~2009-02-10 22:51 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 [this message]
2009-02-10 22:59     ` Mikkel Fahnøe Jørgensen
2009-02-11 11:48 ` Romain Bardou

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=3a360f590902101451m41eff2efx42de4cde14f0058d@mail.gmail.com \
    --to=hcarty@atmos.umd.edu \
    --cc=caml-list@yquem.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).