caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: oasis packaging questions
Date: Mon, 12 Mar 2012 09:38:33 +0900	[thread overview]
Message-ID: <4F5D4589.40206@riken.jp> (raw)
In-Reply-To: <DD8AC4F3-F9B3-4DBA-8D4A-E82A6F2849A6@recoil.org>

On 03/09/2012 09:22 PM, Anil Madhavapeddy wrote:
> On 8 Mar 2012, at 22:26, Sylvain Le Gall wrote:
>>
>> 2012/3/8 Adrien<camaradetux@gmail.com>:
>>> Hi,
>>>
>>> On 08/03/2012, Sylvain Le Gall<sylvain@le-gall.net>  wrote:
>>>> Hi,
>>>>
>>>> 2012/3/8 Daniel Bünzli<daniel.buenzli@erratique.ch>:
>>>>> Le jeudi, 8 mars 2012 ŕ 09:31, Sylvain Le Gall a écrit :
>>>>>> setup.ml will be enough for me ;-) But I am biased.
>>>>>
>>>>> For distribution, I'm fine with that aswell. For developement setup.ml
>>>>> takes too much time to invoke (adds an overhead of 0.5s on my system).
>>>>>
>>>>
>>>> That the parsing time because the file is big. I know this issue and
>>>> will try to improve that in the future. I think a 50% down size is
>>>> possible, that will bring this time to 250ms. Although, I don't think
>>>> that even for development env a 500ms delay is that big... I doubt to
>>>> be able to reduce to ~0s.
>>>
>>> For my own stuff, I've been using a Makefile which includes a rule to
>>> (re)compile setup.ml into an executable with ocamlc.opt (compiling
>>> with ocamlopt was too slow). My usual development machine isn't
>>> terribly fast and this has helped a lot.
>>>
>>> I think there was a mention of an issue though but it can help a lot.
>>
>> Make sense. So super quick hack!
>>
>> Add at the beginning of setup.ml:
>
> A Makefile works just fine (and making the autogenerated code less complex
> rather than more would be better).

May I suggest to generate an OcamlMakefile instead of a plain Makefile? :)
It might be simpler to generate, I think.

> This is the template Makefile I use:
> https://github.com/avsm/ocaml-github/blob/master/Makefile
>
> -anil
>


  parent reply	other threads:[~2012-03-12  0:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  0:26 [Caml-list] " Daniel Bünzli
2012-03-08  8:31 ` [Caml-list] " Sylvain Le Gall
2012-03-08 15:36   ` Daniel Bünzli
2012-03-08 20:13     ` Sylvain Le Gall
2012-03-08 20:59       ` Daniel Bünzli
2012-03-08 21:27         ` Sylvain Le Gall
2012-03-08 22:39           ` Daniel Bünzli
2012-03-09 11:56             ` Gerd Stolpmann
2012-03-09 13:53               ` Daniel Bünzli
2012-03-09 18:42           ` Daniel Bünzli
2012-03-09 19:11             ` Sylvain Le Gall
2012-03-09 19:49               ` Daniel Bünzli
2012-03-09 20:35               ` Daniel Bünzli
2012-03-09 21:06                 ` Sylvain Le Gall
2012-03-08 21:40       ` Adrien
2012-03-08 22:26         ` Sylvain Le Gall
2012-03-08 22:59           ` Daniel Bünzli
2012-03-09 12:22           ` Anil Madhavapeddy
2012-03-09 13:01             ` Wojciech Meyer
2012-03-12  0:38             ` Francois Berenger [this message]
2012-03-16 13:56     ` Damien Doligez
2012-03-08 16:09 ` [Caml-list] " Jérémie Dimino
2012-03-08 16:19   ` Gerd Stolpmann
2012-03-08 21:10     ` [Caml-list] " Sylvain Le Gall
2012-03-08 16:36   ` [Caml-list] " Daniel Bünzli
2012-03-08 16:58     ` Jérémie Dimino
2012-03-08 19:11       ` Daniel Bünzli
2012-03-09  6:40   ` Stéphane Glondu

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=4F5D4589.40206@riken.jp \
    --to=berenger@riken.jp \
    --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).