From: "François Bobot" <francois.bobot@cea.fr>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] Dependencies between plugins
Date: Tue, 03 Mar 2015 14:15:35 +0100 [thread overview]
Message-ID: <54F5B3F7.3030705@cea.fr> (raw)
Hi everyone,
I'm wondering how people are handling dependencies between libraries dynamically linked.
Even if many libraries compile a cmxs and have in their META file `archive(plugin,native)=...`. I
know only one tool that uses this information: the ocsigen server. The code to gather all the cmxs
or cma is not hard to write, thanks to findlib:
https://github.com/ocsigen/ocsigenserver/blob/master/src/baselib/ocsigen_loader.ml#L165
Does someone wrote a library that does that?
Gerd, do you think that something that does that could be added to ocamlfind? One tricky thing is to
know the library statically linked (ie. `Ocsigen_config.builtin_packages`), perhaps ocamlfind can
during linking add this information.
Regards,
--
François
next reply other threads:[~2015-03-03 13:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 13:15 François Bobot [this message]
2015-03-03 13:40 ` Gabriel Scherer
2015-03-03 14:23 ` François Bobot
2015-03-03 14:31 ` Maxence Guesdon
2015-03-03 14:32 ` Ivan Gotovchits
2015-03-03 14:42 ` Sebastien Mondet
2015-03-03 15:02 ` François Bobot
2015-03-03 15:24 ` Sebastien Mondet
2015-03-03 14:51 ` François Bobot
2015-03-03 14:55 ` Gerd Stolpmann
2015-03-04 9:58 ` François Bobot
2015-04-13 19:27 ` Ivan Gotovchits
2015-04-13 19:29 ` Gerd Stolpmann
2015-04-14 8:59 ` François Bobot
2015-04-14 9:47 ` Stéphane Glondu
2015-04-14 12:45 ` François Bobot
2015-04-27 9:51 ` Gerd Stolpmann
2015-04-27 10:16 ` Gabriel Scherer
2015-04-27 12:16 ` François Bobot
2015-04-27 12:32 ` Daniel Bünzli
2015-04-29 12:00 ` Gerd Stolpmann
2015-04-27 11:55 ` François Bobot
[not found] ` <1735_1425463114_54F6D748_1735_16789_8_54F6D731.3090004@cea.fr>
2015-03-06 11:45 ` François Bobot
2015-04-14 12:21 ` Gabriel Kerneis
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=54F5B3F7.3030705@cea.fr \
--to=francois.bobot@cea.fr \
--cc=caml-list@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