From: Romain Bardou <Romain.Bardou@lri.fr>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: Romain Bardou <Romain.Bardou@lri.fr>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ocamlbuild with findlib + camlp4
Date: Fri, 07 Mar 2008 10:26:35 +0100 [thread overview]
Message-ID: <47D10A4B.7000904@lri.fr> (raw)
In-Reply-To: <318509.18876.qm@web54603.mail.re2.yahoo.com>
> Anyway, ideally one should be able to specify in the _tags file the findlib
> packages that each ml file depends upon.
Well, doesn't the following plugin do what you want?
###########################
open Ocamlbuild_plugin
open Command
(* list of packages *)
let packages = ["nums"; "str"; "unix"]
(* ocamlfind command *)
let ocamlfind x = S[A"ocamlfind"; x]
let _ = dispatch begin function
| Before_options ->
Options.ocamlc := ocamlfind & A"ocamlc";
Options.ocamlopt := ocamlfind & A"ocamlopt";
Options.ocamldep := ocamlfind & A"ocamldep";
Options.ocamldoc := ocamlfind & A"ocamldoc"
| After_rules ->
flag ["ocaml"; "link"; "linkpkg"] & A"-linkpkg";
List.iter
(fun pkg -> flag ["ocaml"; "pkg_"^pkg] & S[A"-package"; A pkg])
packages
| _ -> ()
end
###########################
This tells Ocamlbuild to use ocamlfind, and also defines some tags:
* The "linkpkg" tag, which adds the "-linkpkg" flag when linking. Tag
your output files with it (your .byte or .native files), not the source
files.
* The "pkg_nums", "pkg_str", and "pkg_unix" tags (simply add packages to
the "packages" list if you need other packages) which add the "-package
nums", "-package str" and "-package unix" options respectively. Tag your
source files with the -package options they should use when compiling,
and your output files with the -package options they should use when
linking.
As an exercise you could even add a tag "ocamlfind" which would allow
you to use ocamlfind only when you want to.
Now you should be able to use ocamlfind with different options depending
on tags.
Disclaimer:
* I know it compiles but I didn't have time to construct a dummy project
which would allow me to test this extension.
* It does nothing to handle camlp4, but you should be able to add the
correct options yourself.
Please tell me if it is what you needed or not :)
--
Romain Bardou
next prev parent reply other threads:[~2008-03-07 9:24 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
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 [this message]
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=47D10A4B.7000904@lri.fr \
--to=romain.bardou@lri.fr \
--cc=caml-list@yquem.inria.fr \
--cc=darioteixeira@yahoo.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