From: SF Markus Elfring <elfring@users.sourceforge.net>
To: caml-list@inria.fr
Subject: [Caml-list] Development status of the dependency generator for OCaml
Date: Tue, 18 Jul 2017 21:21:35 +0200 [thread overview]
Message-ID: <8e0dbe2f-3ff2-5f56-7d81-89f1eaad041b@users.sourceforge.net> (raw)
Hello,
I took a closer look at data which the tool “ocamldep” can provide.
* Compiled module interfaces (CMI files) do not depend on interface
descriptions (MLI files) there.
Is such dependency information interpreted as an optional detail?
* Compiled modules do also not depend on OCaml sources (ML files) there.
Some of the generated make specifications indicate only a dependency on
a single compiled module interface.
Do you expect that dependency data should be exported completely?
Another view:
It is usually expected that some dependencies can be handled by implicit
make rules. So I imagine that the provided data should only contain
extensions for the desired software build rules.
https://www.gnu.org/software/make/manual/html_node/Multiple-Rules.html
It seems that a bit of data is written too much so far according to this usage.
How would you like to improve the software situation further?
Regards,
Markus
next reply other threads:[~2017-07-18 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 19:21 SF Markus Elfring [this message]
2017-07-21 9:19 ` David Allsopp
2017-07-21 11:30 ` SF Markus Elfring
2017-07-21 13:01 ` David Allsopp
2017-07-21 15:50 ` SF Markus Elfring
2017-07-21 16:16 ` David Allsopp
2017-07-21 17:07 ` SF Markus Elfring
2017-07-25 18:13 ` [Caml-list] Addition of a data export variant containing only required extensions for build dependency specifications SF Markus Elfring
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=8e0dbe2f-3ff2-5f56-7d81-89f1eaad041b@users.sourceforge.net \
--to=elfring@users.sourceforge.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).