From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] Mapping between ocamlbuild and ocamlc versions
Date: Wed, 4 Jul 2018 16:03:14 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A177880AC00@IRSMSX102.ger.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
Dear OCaml Team,
I wonder if there is a mapping table between ocamlbuild github labels and ocamlc versions. As far as I understand after ocamlbuild 4.02.3 a new labeling/versioning scheme was introduced for ocamlbuild which currently appears to be at 0.12.0.
Which label of ocamlbuild am I supposed to use with ocaml 4.06? Is it so that unless I have special requirements to ocamlbuild I can use ocamlbuild label 4.02.3 for any newer version of ocaml? Is this the recommended way of doing it?
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #2: Type: text/html, Size: 2885 bytes --]
next reply other threads:[~2018-07-04 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 16:03 Soegtrop, Michael [this message]
2018-07-04 16:24 ` David Allsopp
2018-07-04 21:31 ` Soegtrop, Michael
2018-07-04 22:00 ` David Allsopp
2018-07-05 8:04 ` Soegtrop, Michael
2018-07-05 18:23 ` Evgeny Roubinchtein
2018-07-05 18:28 ` Bernhard Schommer
2018-07-08 22:03 ` Richard W.M. Jones
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=0F7D3B1B3C4B894D824F5B822E3E5A177880AC00@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.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).