caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dmitry Grebeniuk <gdsfh1@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] Re: ocamlbuild + Coq
Date: Fri, 11 May 2012 12:54:12 +0300	[thread overview]
Message-ID: <CAPi0vKVt1JaOc6sr66WL7ZMYhQxL6U-XgFNDO0RbzY5pY2WE4Q@mail.gmail.com> (raw)
In-Reply-To: <CAPi0vKVSpEPdFGL55JFRa=qcVG_ot4U74-R1_LHQVs81Pb5rpQ@mail.gmail.com>

Hello.

  I've asked about ocamlbuild on irc, but without any success,
so I'll try to ask in caml-list now.

>  Has anybody tried to compile OCaml + Coq project with ocamlbuild?

  Here is an attempt to make plugin:

https://bitbucket.org/gds/ocamlbuild-coq-attempt

, but the plugin doesn't work as expected: it fails to use rule
"ocaml: mli -> cmi" to produce String0.cmi from the existing
String0.mli file.  If you run script "./run.sh" from repository,
you'll see the problem.

  ygrek gave me the idea that ocamlbuild doesn't see
_build/String0.mli because it doesn't know that this file
was produced by extraction (it seems that ocamlbuild
internally stores known files from _build directory).
  I have no way to tell ocamlbuild in advance which
files will be produced extracting the .v file.
  Maybe there are ways to tell ocamlbuild "just use _build
contents without questions" or "rescan _build directory"?
Or maybe there are other ways to deal with this issue?

  (the ultimate goal of this plugin is to have source .v and .ml
files in project's source tree, without any Coq-extracted
intermediate .ml files, which should reside in _build.)


  reply	other threads:[~2012-05-11  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 12:30 [Caml-list] " Dmitry Grebeniuk
2012-05-11  9:54 ` Dmitry Grebeniuk [this message]
2012-05-11 10:22   ` [Caml-list] " Romain Bardou

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=CAPi0vKVt1JaOc6sr66WL7ZMYhQxL6U-XgFNDO0RbzY5pY2WE4Q@mail.gmail.com \
    --to=gdsfh1@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).