From: Christian Sternagel <Christian.Sternagel@uibk.ac.at>
To: caml-list@inria.fr
Subject: generating .cma-files with ocamlbuild
Date: Sat, 24 Mar 2007 16:11:28 +0100 [thread overview]
Message-ID: <1174749088.46053fa061126@web-mail1.uibk.ac.at> (raw)
Is there an easy way to tell ocamlbuild that it should
take some *.ml and *.mli files and build an archive
<name>.cma out of them?
Btw: I have another question concerning *.cma files.
Maybe an example is the easiest way to express this
question.
There are files:
set.mli set.ml setInternal.ml a.mli a.ml
I want to create the file util.cma which contains
set.cmo, setInternal.cmo, and a.cmo.
set.cmo uses setInternal.cmo but the user should
only be able to access modules Set and A but not
SetInternal. As far as I understud, this is done by
just providing set.cmi and a.cmi together with
util.cma.
Questions:
1) Is my understandung correct?
2) Can there be a problem if somebody using util.cma
(who does not know, that setInternal.cmo is part of
it) uses a self-made module by the name SetInternal
in his application?
cheers
christian
next reply other threads:[~2007-03-24 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 15:11 Christian Sternagel [this message]
2007-03-24 15:26 ` [Caml-list] " Alain Frisch
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=1174749088.46053fa061126@web-mail1.uibk.ac.at \
--to=christian.sternagel@uibk.ac.at \
--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