From: moosotc@gmail.com
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Interface(.mli) location
Date: Mon, 08 Aug 2016 20:16:00 +0300 [thread overview]
Message-ID: <87y447npv3.fsf@gmail.com> (raw)
In-Reply-To: <CAPFanBFYDnUjR4c1cUykoT8ekVM4ozOchzBHZi_URkXEimZLZw@mail.gmail.com> (Gabriel Scherer's message of "Mon, 8 Aug 2016 19:03:34 +0200")
Gabriel Scherer <gabriel.scherer@gmail.com> writes:
> It is correct that ocamldep assumes that the .ml and .mli of a given
> module are at the same place, but this is not the case for the rest of
> the compilation chain, which is either concerned with single source
> files (a .ml file or a .mli file) or with "compilation units" (a .cmo
> and .cmi files passed together, independently of where their source
> files were). In particular, all type-checking tools do look in -I
> directories to find .cmi files for the dependencies of the module
> being compiled (and at this stage they do not care for .mli files).
But the script seems to (somewhat) contradict this, i.e. after `ocamlc
-I d -c a.ml' ocamlc ignores the presence of .mli inside subdirectory
d/, producing both .cmi/.cmo when when compiling a.ml.
[..snip..]
--
mailto:moosotc@gmail.com
next prev parent reply other threads:[~2016-08-08 17:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 16:09 moosotc
2016-08-08 17:03 ` Gabriel Scherer
2016-08-08 17:12 ` Gerd Stolpmann
2016-08-08 17:16 ` moosotc [this message]
2016-08-08 18:30 ` David Allsopp
2016-08-08 18:57 ` moosotc
2016-08-08 19:39 ` David Allsopp
2016-08-08 19:59 ` moosotc
2016-08-08 22:54 ` David Allsopp
2016-08-09 8:45 ` SF Markus Elfring
2016-08-09 16:26 ` David Allsopp
2016-08-09 17:55 ` SF Markus Elfring
2016-08-09 10:56 ` moosotc
2016-08-09 11:43 ` moosotc
2016-08-09 11:46 ` moosotc
2016-08-09 18:08 ` David Allsopp
2016-08-09 18:35 ` moosotc
2016-08-09 18:59 ` David Allsopp
2016-08-09 19:55 ` moosotc
2016-08-10 8:20 ` David Allsopp
2016-08-10 10:38 ` moosotc
2016-08-09 18:33 ` David Allsopp
2016-08-09 18:38 ` moosotc
2016-08-09 19:02 ` David Allsopp
2016-08-09 9:22 ` SF Markus Elfring
2016-08-09 16:32 ` David Allsopp
2016-08-09 18:10 ` SF Markus Elfring
2016-08-09 18:26 ` David Allsopp
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=87y447npv3.fsf@gmail.com \
--to=moosotc@gmail.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
/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).