From: Martin DeMello <martindemello@gmail.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] why is building ocaml hard?
Date: Sat, 9 Jul 2016 21:16:47 -0700 [thread overview]
Message-ID: <CAFrFfuHCXbXxOWi2m11+NsmxX6Av3WNkK=PUh8x6on0NWgD7CQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
My consistent experience with OCaml has been that the build systems are
fiddly and hard to work with, but I've never seen a discussion of why this
is so (as opposed to problems with specific build tools). Supposing you
were to start from scratch and develop a new build system in a bottom up
manner, starting with a set of libraries and utilities and working your way
up to a framework or dsl, what would the difficult steps be?
martin
[-- Attachment #2: Type: text/html, Size: 605 bytes --]
next reply other threads:[~2016-07-10 4:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 4:16 Martin DeMello [this message]
2016-07-10 11:03 ` Gerd Stolpmann
2016-07-10 11:33 ` [Caml-list] Is there an efficient precise ocamldep - Was: " Gerd Stolpmann
2016-07-10 11:51 ` Petter A. Urkedal
2016-07-10 22:41 ` [Caml-list] " Tom Ridge
2016-07-11 6:15 ` Martin DeMello
2016-07-11 7:22 ` Frédéric Bour
2016-07-11 10:36 ` Gerd Stolpmann
2016-07-13 12:10 ` David Allsopp
2016-07-11 9:14 ` Malcolm Matalka
2016-07-12 8:18 ` Goswin von Brederlow
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='CAFrFfuHCXbXxOWi2m11+NsmxX6Av3WNkK=PUh8x6on0NWgD7CQ@mail.gmail.com' \
--to=martindemello@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).