From: Vincent Balat <vincent.balat@univ-paris-diderot.fr>
To: caml-list@inria.fr
Cc: "Till Crueger" <Till.Crueger@gmx.net>
Subject: Re: [Caml-list] Howto link cmas with Ocamlbuild
Date: Thu, 28 Oct 2010 13:41:29 +0200 [thread overview]
Message-ID: <201010281341.30325.vincent.balat@univ-paris-diderot.fr> (raw)
In-Reply-To: <op.vk98i3aysoui26@mail.gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
Hi,
It is not a good idea to include batteries and sexplib in your cma.
If your cma is a findlib package (i.e. has a META file with the right
dependencies inside), Ocsigen server will automatically load the dependencies
if you write
<library findlib-package="yourpackage"/>
or
<eliom findlib-package="yourpackage" />
in Ocsigen server's configuration file.
If your package does not have a META file, you need to load batteries and
sexplib manually:
<library findlib-package="batteries"/>
<library findlib-package="sexplib"/>
Vincent
> Hi,
>
> I am working on a small project that is going to include a dynamic
> webserver using Ocsigen and Eliom. I am using Ocamlbuild for the
> compilation. The project is also going to use Batteries and Sexplib. This
> means I need to include Sexplib and Batteries within the .cma file for
> Ocsigen to find the libraries. However when I use the Myocamlbuild plugin
> for Batteries the rules for linking cmas wont use linkpkg flag. Right now
> I compile the full project using ocamlbuild and then I have to repeat the
> last step manually. Is there a better way, to get ocamlbuild to include
> the necessary libraries in the .cma?
>
> Thank you,
> Till
[-- Attachment #2: Type: text/html, Size: 6316 bytes --]
prev parent reply other threads:[~2010-10-28 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 10:53 Till Crueger
2010-10-28 11:41 ` Vincent Balat [this message]
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=201010281341.30325.vincent.balat@univ-paris-diderot.fr \
--to=vincent.balat@univ-paris-diderot.fr \
--cc=Till.Crueger@gmx.net \
--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;
as well as URLs for NNTP newsgroup(s).