caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] META file standards for ppx extensions
Date: Thu, 9 Apr 2015 17:33:33 +0200	[thread overview]
Message-ID: <46483E4AF51B46A3B3F91B3B5CFE8249@erratique.ch> (raw)
In-Reply-To: <d8a23c877189537c81524be5df2b4377@nleyten.com>

In the assemblage project we are quite interested in seeing packages as named entities providing flags/and or objects to use in a given command execution context (defined as pre-processing, compiling, linking, etc. see [1] for more details).

During the first build ("configure") we want to `ocamlfind query` packages for the right flags in each context and cache them so that we don't have to go through ocamlfind during the compilation (which slows down things quite a bit). 

Is there an invocation that allow us to get the flags or objects to use, the following don't seem to work:

> ocamlfind query -predicates ppx -pp lwt.ppx
> ocamlfind query -pp lwt.ppx 


and I don't see an obvious specifier for `-format` I can use. 

It would be nice in general if ocamlfind would allow us to use `ocamlfind query` in obvious ways so that we can exactly reproduce what it does when whatever `ocamlfind TOOL -pkg PKG1,PKG2,PKG3` is being invoked. 

I'm not working on this at the moment and don't have these things in my head but I remember that it proved to be quite challenging (if not impossible) to achieve that goal. 

Best,

Daniel

[1] http://samoht.github.io/assemblage/Assemblage.Ctx.html



  reply	other threads:[~2015-04-09 15:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 18:20 Dario Teixeira
2015-04-08 18:59 ` Drup
2015-04-08 19:59   ` Dario Teixeira
2015-04-08 20:37     ` Daniel Bünzli
2015-04-09 10:07       ` Dario Teixeira
2015-04-09 10:56     ` Gerd Stolpmann
2015-04-09 12:24       ` Dario Teixeira
2015-04-09 15:33         ` Daniel Bünzli [this message]
2015-04-09 16:45           ` Gerd Stolpmann
2015-04-09 17:27             ` Daniel Bünzli
2015-04-09 18:05               ` Daniel Bünzli
2015-04-09 22:26                 ` Gerd Stolpmann
2015-04-09 22:21               ` Gerd Stolpmann
2015-04-09 23:06                 ` Daniel Bünzli
2015-04-10  8:53                   ` François Bobot
2015-04-10  9:42                     ` Daniel Bünzli
2015-04-10 10:09                       ` Alain Frisch
2015-04-10 11:45                         ` Thomas Gazagnaire
2015-04-10 11:04                       ` François Bobot
2015-04-10 11:55                         ` Daniel Bünzli
2015-04-10 16:33                           ` François Bobot
2015-04-10 17:43                             ` Daniel Bünzli
2015-04-12  6:00                       ` Anil Madhavapeddy
2015-04-10 11:25                   ` Gerd Stolpmann
2015-04-10 11:55                     ` Daniel Bünzli
2015-04-09 15:45         ` Thomas Gazagnaire
2015-04-09 16:28           ` Dario Teixeira
2015-04-09 16:51             ` Gerd Stolpmann
2015-04-10 12:23         ` Daniel Bünzli
2015-04-10 14:55           ` Gerd Stolpmann

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=46483E4AF51B46A3B3F91B3B5CFE8249@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    --cc=dario.teixeira@nleyten.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).