From: "Matej Košík" <5764c029b688c1c0d24a2e97cd764f@gmail.com>
To: caml-list@yquem.inria.fr
Subject: [Caml-list] a question about "ocamlopt" and "ocamldep"
Date: Tue, 13 Mar 2012 18:19:41 +0000 [thread overview]
Message-ID: <4F5F8FBD.5060205@gmail.com> (raw)
Hi,
The "ocamldep" tool generates Makefile dependencies for both situations:
- when we use "ocamlc"
- as well as when we use "ocamlopt"
Dependencies, generated for "*.cmo" files,
are corresponding "*.cmi" files.
This is not surprising.
However, dependencies, generated for "*.cmx" files,
are always other "*.cmx" files.
This is surprising.
Why "*.cmx" files do not depend on "*.cmi" files?
I have noticed this in a bigger project but this phenomenon appear to
happen for arbitrarily small projects.
Consider the following ocamldep-generated couple of rules:
src/ml2c/typing/printtyp.cmo: src/ml2c/typing/types.cmi \
src/ml2c/typing/primitive.cmi src/ml2c/typing/predef.cmi \
src/ml2c/typing/path.cmi src/ml2c/typing/outcometree.cmi \
src/ml2c/typing/oprint.cmi src/ml2c/utils/misc.cmi \
src/ml2c/parsing/longident.cmi src/ml2c/typing/ident.cmi \
src/ml2c/typing/env.cmi src/ml2c/typing/ctype.cmi \
src/ml2c/utils/clflags.cmi src/ml2c/typing/btype.cmi \
src/ml2c/parsing/asttypes.cmi src/ml2c/typing/printtyp.cmi
src/ml2c/typing/printtyp.cmx: src/ml2c/typing/types.cmx \
src/ml2c/typing/primitive.cmx src/ml2c/typing/predef.cmx \
src/ml2c/typing/path.cmx src/ml2c/typing/outcometree.cmx \
src/ml2c/typing/oprint.cmx src/ml2c/utils/misc.cmx \
src/ml2c/parsing/longident.cmx src/ml2c/typing/ident.cmx \
src/ml2c/typing/env.cmx src/ml2c/typing/ctype.cmx \
src/ml2c/utils/clflags.cmx src/ml2c/typing/btype.cmx \
src/ml2c/parsing/asttypes.cmx src/ml2c/typing/printtyp.cmi
The second rule seems to be unnecessarily demanding (unless it makes no
sense to compile *.cmi files if we use ocamlopt). It should read:
src/ml2c/typing/printtyp.cmx: src/ml2c/typing/types.cmi \
src/ml2c/typing/primitive.cmi src/ml2c/typing/predef.cmi \
src/ml2c/typing/path.cmi src/ml2c/typing/outcometree.cmi \
src/ml2c/typing/oprint.cmi src/ml2c/utils/misc.cmi \
src/ml2c/parsing/longident.cmi src/ml2c/typing/ident.cmi \
src/ml2c/typing/env.cmi src/ml2c/typing/ctype.cmi \
src/ml2c/utils/clflags.cmi src/ml2c/typing/btype.cmi \
src/ml2c/parsing/asttypes.cmi src/ml2c/typing/printtyp.cmi
Shouldn't it?
next reply other threads:[~2012-03-13 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 18:19 Matej Košík [this message]
2012-03-13 18:34 ` Matthias Puech
2012-03-13 19:26 ` Gabriel Scherer
2012-03-14 10:31 Matej Košík
2012-03-14 11:23 ` Gabriel Scherer
2012-03-14 12:38 ` Matej Košík
2012-03-14 13:19 ` Virgile Prevosto
2012-03-14 17:12 ` Gabriel Scherer
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=4F5F8FBD.5060205@gmail.com \
--to=5764c029b688c1c0d24a2e97cd764f@gmail.com \
--cc=caml-list@yquem.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).