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] ocamlbuild + Coq
Date: Tue, 8 May 2012 15:30:24 +0300	[thread overview]
Message-ID: <CAPi0vKVSpEPdFGL55JFRa=qcVG_ot4U74-R1_LHQVs81Pb5rpQ@mail.gmail.com> (raw)

Hello.

  Has anybody tried to compile OCaml + Coq project with ocamlbuild?
Maybe you can share myocamlbuild.ml rules for such compilation?
(I already wrote simple rule on "%.v" -> "%.ml", but dependencies'
discovering is killing me, so I'm asking here, maybe there are some
ready solutions.)

  I know about coq_makefile, but I don't want to pollute source tree with
intermediate extraction results.  I could ignore/remove .vo/.glob files,
but Coq extracts some .ml files from his stdlib, so I see no sane way
to ignore some .ml files while not-ignoring other .ml files.

             reply	other threads:[~2012-05-08 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 12:30 Dmitry Grebeniuk [this message]
2012-05-11  9:54 ` [Caml-list] " Dmitry Grebeniuk
2012-05-11 10:22   ` 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='CAPi0vKVSpEPdFGL55JFRa=qcVG_ot4U74-R1_LHQVs81Pb5rpQ@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).