caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Francois Berenger <francois.berenger@inria.fr>
To: Jacques-Pascal Deplaix <jp.deplaix@gmail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] One build system to rule them all?
Date: Wed, 10 Sep 2014 15:55:23 +0200	[thread overview]
Message-ID: <5410584B.8090302@inria.fr> (raw)
In-Reply-To: <541057C6.702@gmail.com>

On 09/10/2014 03:53 PM, Jacques-Pascal Deplaix wrote:
> Hi,
>
> I did know obuild but I forgot a fact about it: it doesn't use ocamlfind.
>
> As you took the defense of obuild, do you know why it doesn't use it ? I
> think I know how it works for simple packages but how is it supposed to
> work with packages which uses the linkopts field or even if the cma has
> not the same name as the library itself ? Why not having used findlib
> (for the speed declaimed in DESIGN.md) ?

I don't know, I am just an obuild user, not a real contributor.

> Did I missed something ?
>
> Cheers,
>
> On 09/10/2014 03:29 PM, Francois Berenger wrote:
>> On 09/10/2014 02:49 PM, Yotam Barnoy wrote:
>>> It appears to me that every couple of months we hear of someone
>>> implementing yet another build system in ocaml. Given the success of
>>> opam, I think it's clear that sometimes a monolithic solution, behind
>>> which the entire community can organize, is the best solution --
>>> especially for infrastructure. Looking at haskell, having cabal as the
>>> main build system has really helped them advance in terms of supporting
>>> other platforms (such as windows), and since all community efforts in
>>> this realm are focused on cabal, they can improve it rapidly.
>>>
>>> a. Is there any build system we can organize behind to crown as the
>>> official build system?
>>> b. What are the use-cases missing from specific build systems, that have
>>> driven people to use other build systems?
>>> c. To pick one possible candidate, if ocamlbuild were spun out of the
>>> compiler, could it be enhanced to cover all the main use-cases so
>>> (almost) everyone would be happy with it?
>>>
>>> It's just such a shame to see the ocaml community re-inventing the wheel
>>> over and over again, each time with some limitation so that the next
>>> person needs to do the same thing yet again.
>>
>> It is not a shame, it is a tradition in the ocaml community! :-D
>> For example, almost each ocaml programmer that I know of have written
>> a logger (me included, it's even in opam so that I can reinvent
>> another wheel next time).
>>
>> More seriously, concerning build systems, we clearly have quite some
>> choice on the OCaml shelf:
>> - obuild
>> - ocamlbuild
>> - omake
>> - oasis (which in fact uses ocamlbuild, don't forget that)
>> - jenga
>> - [...]
>>
>> My preffered is obuild (https://github.com/ocaml-obuild/obuild),
>> for the terseness, readability and centralization of its build
>> descriptions. I would love to see the user community of obuild grow,
>> so that we can get rid of more bugs, be able to compile _any_
>> OCaml project with it and implement even more cool features
>> (contributors are very welcome).
>>
>> I don't want a ring to rule them all, jut a ring that fits _my_
>> finger. ;)
>>
>

-- 
Regards,
Francois.

  reply	other threads:[~2014-09-10 13:55 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 [this message]
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
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=5410584B.8090302@inria.fr \
    --to=francois.berenger@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=jp.deplaix@gmail.com \
    /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).