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 9580E81799 for ; Thu, 25 Jul 2013 17:10:56 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of sylvain@le-gall.net) identity=pra; client-ip=80.91.229.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="sylvain@le-gall.net"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of gclci-caml-list@m.gmane.org designates 80.91.229.3 as permitted sender) identity=mailfrom; client-ip=80.91.229.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="gclci-caml-list@m.gmane.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of postmaster@plane.gmane.org designates 80.91.229.3 as permitted sender) identity=helo; client-ip=80.91.229.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="postmaster@plane.gmane.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiQDAGA/8VFQW+UDgWdsb2JhbABagzu/QxYOAQEWJiiCJAEBBXQVCxguECwbGRQFh3u5U5Aag2oDmQiTOA X-IPAS-Result: AiQDAGA/8VFQW+UDgWdsb2JhbABagzu/QxYOAQEWJiiCJAEBBXQVCxguECwbGRQFh3u5U5Aag2oDmQiTOA X-IronPort-AV: E=Sophos;i="4.89,744,1367964000"; d="scan'208";a="27316139" Received: from plane.gmane.org ([80.91.229.3]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/AES256-SHA; 25 Jul 2013 17:10:55 +0200 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1V2NBt-000174-T5 for caml-list@inria.fr; Thu, 25 Jul 2013 17:10:53 +0200 Received: from root.ovh.le-gall.net ([37.59.37.175]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 25 Jul 2013 17:10:53 +0200 Received: from sylvain by root.ovh.le-gall.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 25 Jul 2013 17:10:53 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: caml-list@inria.fr From: Sylvain Le Gall Date: Thu, 25 Jul 2013 15:10:37 +0000 (UTC) Message-ID: References: <1374669368.25411.5@samsung> <1B6BB035-9909-4F0C-9DEA-F713B977A467@ocamlpro.com> <7F8931D5-E65D-49EB-B54D-A50716F3EFDD@recoil.org> <51F0801A.5080603@riken.jp> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: root.ovh.le-gall.net User-Agent: slrn/pre1.0.0-18 (Linux) Subject: [Caml-list] Re: GODI is shutting down On 25-07-2013, Francois Berenger wrote: > On 07/25/2013 02:05 AM, Gabriel Scherer wrote: >>> I think that's fair, but the devil is in the details. The core of OASIS >>> is sound, but is hampered by its need to build on top of ocamlfind >>> and ocamlbuild, and the ensuing impedance mismatches that follow (e.g. >>> manually editing _tags files, and trying to debug which tool a failure >>> happens in is an advanced operation). OPAM packages represent an output >>> collection of (several optionally built) ocamlfind packages, and >>> OASIS sits awkwardly in between these two right now, with ocamlbuild >>> crashing the party and getting drunk in the kitchen. >> >> While we're at it (and hoping a diversion might restores some >> constructiveness in this discussion), I have also been thinking about >> this aspect of OASIS that I don't really like. I use ocamlbuild >> -use-ocamlfind, but I'd rather build my _tags and myocamlbuild.ml >> files completely separately from OASIS > > Personnally, I'd rather have a single human-readable file containing all > the build information. > > With the current setup in oasis used by a developper, you get: > a _tags file, a myocamlbuild.ml and you need a Makefile > on top of that (with some parts automatically generated) to pass more > options to ocamlbuild. > Amazing! > But at least I see a clear culprit (ocamlbuild). > It depends a lot. If you use $> oasis setup -setup-update dynamic You generate a very small set of files (no _tags and no myocamlbuild if they are not here). I use that for certain project. I think your problem is that OASIS try to generate standalone installation (i.e. a package that doesn't depend on OASIS to build), which means I have to pre-generate files for ocamlbuild, just as automake... Now, if the community as a whole say that we don't need a standalone generation and can rely on OASIS to build, it would make my life 10x easier (getting rid of super-complex 2-stage setup, ocaml-data-notation, ocamlmod, ocamlify...) Cheers, Sylvain Le Gall -- Website: http://sylvain.le-gall.net/ OCaml forge: http://forge.ocamlcore.org OCaml blogs: http://planet.ocaml.org