caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] One build system to rule them all?
Date: Thu, 18 Sep 2014 17:15:24 -0400	[thread overview]
Message-ID: <CAN6ygO=ixBhG6z=iqEQdUGiTbsPYKU=kCCz4uzwJx2Qba+zsdA@mail.gmail.com> (raw)
In-Reply-To: <5416EAF8.9050800@glondu.net>

[-- Attachment #1: Type: text/plain, Size: 2565 bytes --]

While there was no 'conclusion' to this thread, if I had to come up with
one, it would be that we have a bunch of build tools which are all not
amazing at this point in time. We have some DSL-based build tools and some
ocaml-based build tools, and all of them need a lot of love to get to a
good state.

My personal view is that we (as a community) should work at getting at
least one DSL tool to be really great. I'm sure Jenga (an ocaml-based tool
which seems more like a build-tool engine) will continue to be developed by
Jane Street no matter what, so is there a DSL-based build system that we
can converge on to use and improve? The contenders for this slot appear to
be omake, obuild, and ocp-build. I'm more than willing to switch to one of
these if I know that other people will as well, and that it will be
actively developed (preferably on github). More users = more invested
parties = more development potential. Conversely, continuing to spread the
community's attention between these tools (as well as ocamlbuild, which
seems destined to stagnate) before any one of them is top notch seems to me
to be detrimental to ocaml's health as an ecosystem.

BTW Anil: is assemblage supposed to be an entire build toolchain, or is it
only supposed to write makefiles (as the description in the readme states)?

-Yotam

On Mon, Sep 15, 2014 at 9:34 AM, Stéphane Glondu <steph@glondu.net> wrote:

> Le 10/09/2014 20:59, Yotam Barnoy a écrit :
> > So here are some requirements I can think of (using some of the
> > suggestions that have been brought up):
> > - Easy to use, especially for small projects (large projects can afford
> > to put more time into their build systems)
> > - Abstract away platform considerations as much as possible. No
> > dependence on specific shells and POSIX utilities.
> > - Allows compilation of C files, which is quite common in ocaml packages.
> > - Scalable to many directories and files
> > - Uses ocamlfind to locate packages
> > - Handles camlp4 and ppx
> > - Parallel & incremental compilation
>
>  - Support of platforms without ocamlopt. Many build systems assume that
> ocamlopt is available and have to be called specially (or even patched)
> when it is missing, which complicates packaging on these platforms.
>
> --
> Stéphane
>
> --
> 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: 3360 bytes --]

  reply	other threads:[~2014-09-18 21:15 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 12:49 Yotam Barnoy
2014-09-10 13:00 ` Simon Cruanes
2014-09-10 13:02 ` Adrien Nader
2014-09-10 13:05 ` David Sheets
2014-09-10 14:04   ` Thomas Braibant
2014-09-10 14:13     ` Adrien Nader
2014-09-10 13:18 ` Mark Shinwell
2014-09-10 13:29 ` Francois Berenger
2014-09-10 13:53   ` Jacques-Pascal Deplaix
2014-09-10 13:55     ` Francois Berenger
2014-09-10 14:17   ` Maxence Guesdon
2014-09-10 19:13     ` Drup
2014-09-10 22:56       ` Gerd Stolpmann
2014-09-13 12:01       ` rixed
2014-09-13 12:21         ` Drup
2014-09-13 12:37           ` rixed
2014-09-13 12:50             ` Adrien Nader
2014-09-13 13:05             ` Drup
2014-09-19 11:15       ` Matej Kosik
2014-09-10 14:23   ` Gerd Stolpmann
2014-09-10 15:17     ` Leonardo Laguna Ruiz
2014-09-10 18:59       ` Yotam Barnoy
2014-09-10 19:16         ` Peter Zotov
2014-09-10 19:56           ` Sebastien Mondet
2014-09-10 20:15             ` Gabriel Scherer
2014-09-10 23:20             ` Gerd Stolpmann
2014-09-10 20:13         ` Adrien Nader
2014-09-11  7:53         ` Francois Berenger
2014-09-11 10:37           ` Yaron Minsky
2014-09-12 14:08             ` Yotam Barnoy
2014-09-12 14:31               ` Francois Berenger
2014-09-12 14:36               ` Anil Madhavapeddy
2014-09-12 18:49                 ` Yaron Minsky
2014-09-12 15:10               ` SF Markus Elfring
2014-09-12 15:34               ` Adrien Nader
2014-09-12 18:50               ` Fabrice Le Fessant
2014-09-14 18:46               ` Richard W.M. Jones
2014-09-13 12:22         ` rixed
2014-09-15 13:34         ` Stéphane Glondu
2014-09-18 21:15           ` Yotam Barnoy [this message]
2014-09-18 21:21             ` Anil Madhavapeddy
2014-09-18 21:36               ` Yaron Minsky
2014-09-19 12:31                 ` Daniel Bünzli
2014-09-19 13:06                   ` Anil Madhavapeddy
2014-09-18 21:23             ` Yaron Minsky
2014-09-19  7:27               ` Gabriel Scherer
2014-09-19 15:03                 ` Yaron Minsky
2014-09-12 16:54 ` [Caml-list] Re : " r.3
2014-09-14 18:16 ` [Caml-list] " Richard W.M. Jones
2014-09-19  9:14 ` r.3

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='CAN6ygO=ixBhG6z=iqEQdUGiTbsPYKU=kCCz4uzwJx2Qba+zsdA@mail.gmail.com' \
    --to=yotambarnoy@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).