From: Philippe Veber <philippe.veber@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] oasis, inter-dependent libraries and syntax extension
Date: Mon, 31 Oct 2011 17:23:24 +0100 [thread overview]
Message-ID: <CAOOOohRDB9HFwLqCrXt89-p6mQZgQcs4PqJW42KyiWy79q07fQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
Hi,
I have an oasis project defining three inter-dependent libraries A, B and
C. B is a syntax extension, and depends on A. C depends on both A and B. I
have written an _oasis file for this, which works fine if I don't use the
extension in C, but fails if I do, during ocamldep (ocamldep lacks the
appropriate options to understand the new syntax). Has anybody run into
this problem ?
ph.
[-- Attachment #2: Type: text/html, Size: 416 bytes --]
next reply other threads:[~2011-10-31 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 16:23 Philippe Veber [this message]
2011-10-31 16:40 ` Sebastien Mondet
2011-10-31 20:09 ` Philippe Veber
2011-11-01 10:33 ` Philippe Veber
2011-11-02 10:08 ` [Caml-list] " Sylvain Le Gall
2011-11-02 10:33 ` Philippe Veber
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=CAOOOohRDB9HFwLqCrXt89-p6mQZgQcs4PqJW42KyiWy79q07fQ@mail.gmail.com \
--to=philippe.veber@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