From: Ashish Agarwal <agarwal1975@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] ocamldep and module aliases
Date: Tue, 9 Sep 2014 18:21:03 -0400 [thread overview]
Message-ID: <CAMu2m2J8DcYz1K8UDo7xM9TyevPr-7CxOGuOovSbV=0Y7o0QGw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
Is ocamldep 4.02 supposed to support the -no-alias-deps flag too? It
doesn't, so I'm not sure how to implement the example at the end of Section
7.17 [1] on a real library. Specifically, I use omake, which calls
ocamldep, and I don't see how to avoid it claiming circular dependencies
even though I've added -no-alias-deps to the compilation flags.
[1] http://caml.inria.fr/pub/docs/manual-ocaml/extn.html#s%3Amodule-alias
[-- Attachment #2: Type: text/html, Size: 586 bytes --]
next reply other threads:[~2014-09-09 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 22:21 Ashish Agarwal [this message]
2014-09-10 5:31 ` Jacques Garrigue
2014-09-10 5:37 ` Jacques Garrigue
2014-09-10 11:06 ` Ashish Agarwal
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='CAMu2m2J8DcYz1K8UDo7xM9TyevPr-7CxOGuOovSbV=0Y7o0QGw@mail.gmail.com' \
--to=agarwal1975@gmail.com \
--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).