From: David Allsopp <dra-news@metastack.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Filename.temp_dir_name
Date: Wed, 29 Oct 2014 14:41:17 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9E9670584@Remus.metastack.local> (raw)
In-Reply-To: <20141029143025.GA16501@pema>
Sébastien Hinderer wrote:
> David Allsopp (2014/10/23 12:50 +0000):
<snip>
> Thanks for the pointers. I had a look to the different projects you
> mentionned but so far I couldn't find where in the sources the
> compatibility layer was defined / generated.
>
> I mean, I understand the principle of what you explain but I'd be happy to
> see a concrete example illustrating how the buildsystem generates the
> appropriate files depending on the compiler version.
>
> Would it be possible for you to show me more precisely where this is done,
> plese?
In batteries[1], see src/batUnix.mliv type [open_flag] which has lines prefixed ##. There is the program build/prefilter.ml and then a suffix rule (search for .mliv.mli) in Makefile which generates batUnix.mli.
In findlib[2], see configure (search for "# bytes?"). It detects whether bytes.cmi exists in the compiler's lib directory (`ocamlc -where`/bytes.cmi). Based on that it therefore determines whether it will generate a dummy META file from the files site-lib-src/bytes or whether it will compile its compatibility library in src/bytes.
David
[1] http://forge.ocamlcore.org/frs/?group_id=17
[2] http://download.camlcity.org/download/findlib-1.5.5.tar.gz
next prev parent reply other threads:[~2014-10-29 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 12:12 Sébastien Hinderer
2014-10-23 12:50 ` David Allsopp
2014-10-29 14:30 ` Sébastien Hinderer
2014-10-29 14:41 ` David Allsopp [this message]
2014-10-29 15:29 ` Sébastien Hinderer
2014-10-30 7:35 ` Gabriel Scherer
2014-10-30 9:22 ` Sylvain Pogodalla
2014-10-30 9:40 ` Daniel Bünzli
2014-10-30 9:49 ` David Allsopp
2014-10-30 10:04 ` Daniel Bünzli
2014-10-30 9:44 ` Sébastien Hinderer
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=E51C5B015DBD1348A1D85763337FB6D9E9670584@Remus.metastack.local \
--to=dra-news@metastack.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