From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 706C681799 for ; Fri, 26 Jul 2013 07:29:44 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of nanaki@gmail.com) identity=pra; client-ip=209.85.212.48; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nanaki@gmail.com"; x-sender="nanaki@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of nanaki@gmail.com designates 209.85.212.48 as permitted sender) identity=mailfrom; client-ip=209.85.212.48; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nanaki@gmail.com"; x-sender="nanaki@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-vb0-f48.google.com) identity=helo; client-ip=209.85.212.48; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nanaki@gmail.com"; x-sender="postmaster@mail-vb0-f48.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Al4CAHYI8lHRVdQwk2dsb2JhbABAGoM7RAyrPIloiEKBDggWDgEBAQEHCwsJFAQkgiQBAQQBQAEbEgsBAwELBgULDQ0hIQEBEQEFAQoSBhMSh2sBAwkGDDObH4xPgn+EPQoZJwMKZId0AQUMjQmCZAQHhAADiSqMTIFpgSmKfoNBFimEWhw X-IPAS-Result: Al4CAHYI8lHRVdQwk2dsb2JhbABAGoM7RAyrPIloiEKBDggWDgEBAQEHCwsJFAQkgiQBAQQBQAEbEgsBAwELBgULDQ0hIQEBEQEFAQoSBhMSh2sBAwkGDDObH4xPgn+EPQoZJwMKZId0AQUMjQmCZAQHhAADiSqMTIFpgSmKfoNBFimEWhw X-IronPort-AV: E=Sophos;i="4.89,748,1367964000"; d="scan'208";a="27371829" Received: from mail-vb0-f48.google.com ([209.85.212.48]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 26 Jul 2013 07:29:43 +0200 Received: by mail-vb0-f48.google.com with SMTP id w15so946820vbf.7 for ; Thu, 25 Jul 2013 22:29:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IpP2Fs0ZYRfLnwebLqGpaEe7DZvC4SqIr5FKmXyzJO0=; b=WIX9MSoAoss5oHIlcDxZOTyO6sgLDAJiTrAbKTE92LiIJFlsmqQbrlFwSZ183QEndn iYdSivChtq8MHMVP1V3eYvhWglwQfl83JlW7iQvDrBHITedPUBCNz1tukHVNabRaDT1q BuW/dJm1sp1v1o5IR5nrduYsETDoZTAY94laWN37hxe8+a8W2FWG+ASarDFH1cuTvdul ojH28FhbAKWw5xmQUla+snHJI+RExPz9WyjOkkhEgmSnjSc2AednuxuP5uPotxzXHE5q cto7mcj+eQ6qy/QCAVQe5pD39WY5l1ygnitDi9k3D4ZUe7F6a9+DirTkbnZXsl6r8obF d6uA== MIME-Version: 1.0 X-Received: by 10.58.182.103 with SMTP id ed7mr19932775vec.70.1374816582167; Thu, 25 Jul 2013 22:29:42 -0700 (PDT) Received: by 10.58.31.195 with HTTP; Thu, 25 Jul 2013 22:29:42 -0700 (PDT) In-Reply-To: References: <1374669368.25411.5@samsung> <1B6BB035-9909-4F0C-9DEA-F713B977A467@ocamlpro.com> <7F8931D5-E65D-49EB-B54D-A50716F3EFDD@recoil.org> <51F0801A.5080603@riken.jp> <20130725172359.a40fdfb172b120cadab5544a@gmerlin.de> <20130725200356.GA15673@notk.org> <51F1CD6C.3050305@riken.jp> Date: Thu, 25 Jul 2013 22:29:42 -0700 Message-ID: From: Jeff Meister To: Gabriel Scherer Cc: Caml List Content-Type: multipart/alternative; boundary=047d7b676e1c02f48004e2636e3a Subject: Re: ocamlbuild (was Re: [Caml-list] Re: GODI is shutting down) --047d7b676e1c02f48004e2636e3a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have a codebase that currently depends on an old version of OMake, and I would rather use ocamlbuild instead. As an end user, I see two key advantages: ocamlbuild is part of INRIA's official OCaml distribution, which implies a certain level of commitment to continued support, and ocamlbuild knows all about how to build OCaml projects (even using ocamlfind), so for simple applications it "just works". However, I was reluctant to look into ocamlbuild when it first appeared, since the only documentation was a set of presentation slides. It seemed powerful, but like you, I am not really interested in build systems. I'm more encouraged now that a section has appeared in the OCaml manual. Aside from that, are there any other resources I should look into? I'm wondering if there are some documents, or even mailing list threads, that would help me learn how to customize the building of a complex codebase like you just did in the "which ocaml build system" thread? I'm hoping there is a way to acquire this knowledge that doesn't involve trial and error with the build system. :) On Thu, Jul 25, 2013 at 10:02 PM, Gabriel Scherer wrote: > I am not very interested in build systems. I use one (ocamlbuild) that > I find decent (has several known areas of improvement, but bear with > me), and instead of rewriting a new one from scratch=B9 I decided that > maybe the existing one I could be improved to fix its shortcomings. > You know, by writing bug reports, and more importantly proposing > patches (to the code or the documentation), instead of just > complaining on the mailing-list. I'm not aware, so far, of a major > design problem that can't be incrementally fixed, and whose resolution > is worth the pain of switching to a completely new system. > > =B9: or juggling with three different unannounced build systems; I think > you forgot Jenga and the various adaptations of redo for OCaml; nobody > added OCaml rules to Shake as far as I know, but certainly that will > happen in the future. > > On Fri, Jul 26, 2013 at 3:14 AM, Francois Berenger > wrote: > > On 07/26/2013 05:03 AM, Adrien Nader wrote: > >> > >> Hi, > >> > >> I believe this entry on the bugtracker is worth mentionning: > >> "ocamlbuild should expose common interface as a library" > >> http://caml.inria.fr/mantis/view.php?id=3D5869 > >> > >> More generally, ocamlbuild's development was mostly stalled but has > >> restarted recently. This should allow fixing many issues and > >> shortcomings. > > > > > > There is not only ocamlbuild! > > > > I would love to see projects such as obuild: > > > > https://github.com/vincenthz/obuild > > > > come out of the woods (like an official release announce if it is > > ready for mass consumption) and become the de facto gold standard. > > > > PS: even OCamlPro have written a tool to replace ocamlbuild > > (ocp-build)... > > > > > > -- > > 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 > > -- > 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 > --047d7b676e1c02f48004e2636e3a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I have a codebase that currently depends on an old ve= rsion of OMake, and I would rather use ocamlbuild instead. As an end user, = I see two key advantages: ocamlbuild is part of INRIA's official OCaml = distribution, which implies a certain level of commitment to continued supp= ort, and ocamlbuild knows all about how to build OCaml projects (even using= ocamlfind), so for simple applications it "just works".

However, I was reluctant to look into ocamlbuild when it first ap= peared, since the only documentation was a set of presentation slides. It s= eemed powerful, but like you, I am not really interested in build systems. = I'm more encouraged now that a section has appeared in the OCaml manual= . Aside from that, are there any other resources I should look into? I'= m wondering if there are some documents, or even mailing list threads, that= would help me learn how to customize the building of a complex codebase li= ke you just did in the "which ocaml build system" thread? I'm= hoping there is a way to acquire this knowledge that doesn't involve t= rial and error with the build system. :)


On Thu,= Jul 25, 2013 at 10:02 PM, Gabriel Scherer <gabriel.scherer@gmail.= com> wrote:
I am not very interested in build systems. I= use one (ocamlbuild) that
I find decent (has several known areas of improvement, but bear with
me), and instead of rewriting a new one from scratch=B9 I decided that
maybe the existing one I could be improved to fix its shortcomings.
You know, by writing bug reports, and more importantly proposing
patches (to the code or the documentation), instead of just
complaining on the mailing-list. I'm not aware, so far, of a major
design problem that can't be incrementally fixed, and whose resolution<= br> is worth the pain of switching to a completely new system.

=B9: or juggling with three different unannounced build systems; I think
you forgot Jenga and the various adaptations of redo for OCaml; nobody
added OCaml rules to Shake as far as I know, but certainly that will
happen in the future.

On Fri, Jul 26, 2013 at 3:14 AM, Francois Berenger <berenger@riken.jp> wrote:
> On 07/26/2013 05:03 AM, Adrien Nader wrote:
>>
>> Hi,
>>
>> I believe this entry on the bugtracker is worth mentionning:
>> =A0 =A0"ocamlbuild should expose common interface as a librar= y"
>> =A0 =A0http://caml.inria.fr/mantis/view.php?id=3D5869
>>
>> More generally, ocamlbuild's development was mostly stalled bu= t has
>> restarted recently. This should allow fixing many issues and
>> shortcomings.
>
>
> There is not only ocamlbuild!
>
> I would love to see projects such as obuild:
>
> http= s://github.com/vincenthz/obuild
>
> come out of the woods (like an official release announce if it is
> ready for mass consumption) and become the de facto gold standard.
>
> PS: even OCamlPro have written a tool to replace ocamlbuild
> =A0 =A0 (ocp-build)...
>
>
> --
> Caml-list mailing list. =A0Subscription 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

--
Caml-list mailing list. =A0Subscription management and archives:
ht= tps://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
--047d7b676e1c02f48004e2636e3a--