caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Kerneis <gabriel@kerneis.info>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: Thomas Gazagnaire <thomas@ocamlpro.com>,
	Dagnat Fabien <fabien.dagnat@telecom-bretagne.eu>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] man, doc, … and opam
Date: Mon, 8 Jul 2013 18:18:42 +0100	[thread overview]
Message-ID: <20130708171842.GB4525@kerneis.info> (raw)
In-Reply-To: <DC44114A5DFC437186715D3216D80D88@erratique.ch>

On Mon, Jul 08, 2013 at 04:41:55PM +0100, Daniel Bünzli wrote:
> However now that I decided to go the ocamlbuild only + install file route for
> pure ocaml packages it would be nice if there was a way for ocamlbuild to tell
> us, given an .mllib (or .itarget) file, all the installable artefacts it
> *might* generate as it does actually have that knowledge and I'd prefer not to
> reencode it my scripts.

I fully agree with the request.  For CIL, I do this with a custom rule .mllib ->
.libfiles in myocamlbuild.ml, but it is an ugly hack I am not very proud of (and
in fact no quite sure how reliable it is):
https://github.com/kerneis/cil/blob/develop/myocamlbuild.ml#L7

I've seen reinvented in some Debian packages as well. A unified ocamlbuild +
ocamlfind mechanism would be great here.

Best,
-- 
Gabriel

  reply	other threads:[~2013-07-08 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 15:58 Dagnat Fabien
2013-07-07 17:38 ` Daniel Bünzli
2013-07-08  9:56   ` Thomas Gazagnaire
2013-07-08 15:41     ` Daniel Bünzli
2013-07-08 17:18       ` Gabriel Kerneis [this message]
2013-07-08 21:10         ` Daniel Bünzli

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=20130708171842.GB4525@kerneis.info \
    --to=gabriel@kerneis.info \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --cc=fabien.dagnat@telecom-bretagne.eu \
    --cc=thomas@ocamlpro.com \
    /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).