From: Dario Teixeira <darioteixeira@yahoo.com>
To: Romain Bardou <Romain.Bardou@lri.fr>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ocamlbuild with findlib + camlp4
Date: Thu, 6 Mar 2008 15:31:53 +0000 (GMT) [thread overview]
Message-ID: <318509.18876.qm@web54603.mail.re2.yahoo.com> (raw)
In-Reply-To: <47CEB768.10508@lri.fr>
Hi,
And thanks for the reply.
> Moreover, these lines mean that packages str and so on will only be used
> when your files are tagged with use_pgsql. Is it really what you want?
Yes.
> I have no experience of ocamlbuild with camlp4 extensions but I guess in
> your case I would list all packages correctly in the "let packages =
> ..." definition (unless you don't want to add the -package option for
> every file?), tag my files which use the camlp4 extension with
> "use_pgsql", and add a flag such as:
I've been mucking around with the myocamlbuild.ml plugin but still haven't
managed to achieve what I want. And judging from a previous message by
Nicolas Pouillard, it may be altogether impossible with the current version
of Ocamlbuild.
Anyway, ideally one should be able to specify in the _tags file the findlib
packages that each ml file depends upon. Suppose that by default you wanted
your ml files to use the "extlib,lwt,ocsigen,pgocaml" packages, but you also
had a "database.ml" file that used the PG'OCaml syntax extension, and therefore
should be preprocessed using the instructions in the "pgocaml.statements"
package. I could define a _tags file as something like this:
true: pkg(extlib,lwt,ocsigen,pgocaml)
<database.ml>: camlp4, pkg(pgocaml.statements)
Any thoughts on how this could be achieved? (I'm not even sure if
Ocamlbuild's tags can be parameterised). This would go a long way
towards simplifying the use of syntax extensions that we've been
discussing in the OSR thread.
Thanks in advance,
Dario Teixeira
__________________________________________________________
Sent from Yahoo! Mail.
The World's Favourite Email http://uk.docs.yahoo.com/nowyoucan.html
next prev parent reply other threads:[~2008-03-06 15:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 13:41 Dario Teixeira
2008-03-05 15:08 ` [Caml-list] " Romain Bardou
2008-03-06 15:31 ` Dario Teixeira [this message]
2008-03-06 15:46 ` Pietro Abate
2008-03-06 19:45 ` Dario Teixeira
2008-03-06 22:14 ` Pietro Abate
2008-03-07 9:26 ` Romain Bardou
2008-03-07 14:46 ` Dario Teixeira
2008-03-07 15:01 ` Nicolas Pouillard
2008-03-07 16:12 ` Dario Teixeira
2008-03-08 11:36 ` Nicolas Pouillard
2008-03-10 15:33 ` Dario Teixeira
2008-03-10 16:15 ` Romain Bardou
2008-03-10 21:13 ` Dario Teixeira
2008-03-10 19:56 ` Arnaud Spiwack
2008-03-10 21:15 ` Dario Teixeira
2008-03-11 10:37 ` Nicolas Pouillard
2008-03-11 13:49 ` Romain Bardou
2008-03-11 15:03 ` Romain Bardou
2008-03-11 17:32 ` Dario Teixeira
2008-03-11 20:17 ` Richard Jones
2008-03-11 10:41 ` Nicolas Pouillard
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=318509.18876.qm@web54603.mail.re2.yahoo.com \
--to=darioteixeira@yahoo.com \
--cc=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).