From: "Warp" <warplayer@free.fr>
To: "OCaml" <caml-list@inria.fr>
Subject: [Caml-list] CMA depend
Date: Fri, 15 Feb 2002 21:05:07 +0100 [thread overview]
Message-ID: <000501c1b71f$2f3d24d0$ba00a8c0@warp> (raw)
Usually, dependencies are between cmo / cmi, but you can also build a cma by
using :
> ocamlc -a file.ml -o file.cma
What about dependencies between this cma file and others ?
The problems here are that :
- a cma can be obtained from more than one ml
- target dependencies can be either cmo cmi OR other cma's ( when using
dynlink ).
I'm actually running a project where I have lots of modules - all dynlinked
and built with a single ML file. Thus are called 'plugins'.
I could have first compile ml to cmo and then cmo to cma , but that does not
sound very reasonable.
So I patched the ocamldep tool, adding :
+ print_dependencies (basename ^ ".cma") byt_deps;
on line 405.
Now it works fine, but I'm not sure that's the best way to do it.
Any other idea ?
BTW, the "-native" ocamldep flag can have some use, but what about a
"-bytecode" flag ?
Warp
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
reply other threads:[~2002-02-16 19:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000501c1b71f$2f3d24d0$ba00a8c0@warp' \
--to=warplayer@free.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;
as well as URLs for NNTP newsgroup(s).