Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] from oasis to obuild (original subject was Re: Accelerating compilation)
Date: Tue, 1 Oct 2013 12:25:50 +0000 (UTC)	[thread overview]
Message-ID: <slrnl4lfqn.ntq.sylvain@le-gall.net> (raw)
In-Reply-To: <524A1DF2.1040002@riken.jp>

On 01-10-2013, Francois Berenger <berenger@riken.jp> wrote:
> On 09/30/2013 11:11 PM, Sylvain Le Gall wrote:
>>> oasis setup
>>> ocaml setup.ml -configure
>>> ocaml setup.ml -build
>>>
>>> # time ./build.sh
>>> real    0m9.397s
>>>
>>> Compile time after, with obuild:
>>> # obuild clean && time (obuild configure && obuild build -j 1)
>>> real    0m3.624s
>>>
>>
>> Note that given the proximity of obuild and _oasis files it should be
>> super easy to just convert 1 time the _oasis file to foo.obuild and keep
>> using _oasis while changing the build backend from ocamlbuild to obuild.
>>
>> OASIS is not building anything by itself, the time you report is
>> probably 90% due to ocamlbuild (the build backend).
>
> Sylvain, I fully trust you on this one.
>
> And since I dislike ocamlbuild, I am getting rid of it or tools
> that use it as their default compilation backend.
> obuild seems like the perfect choice to fill my needs.
>
> I do like oasis, but you also know that I started quite early
> to reclaim some other compilation engine to be supported by oasis.

Fair enough, so let make this happen! Are you willing to be a tester or
helping me on the topic. I have seen that there are some tools to handle
_oasis file in obuild, but given there extreme simpicity, I think this
was just a try and probably not working:
https://github.com/vincenthz/obuild/blob/master/tools/assimilate_oasis.ml

Let's grow this into something that work really with _oasis file and
have the possibility to choose a different backend for OASIS.

I have contacted obuild author to see how we can cooperate on the topic
and I would like to do something to have at least another build engine
possible.

Cheers
Sylvain

>
>> BTW, this kind of _oasis -> obuild conversion is a topic I have
>> discussed with the author of obuild and I am 100% willing to do the
>> conversion plugin if it makes sense.
>>
>>
>> Regards
>> Sylvain
>>
>>> --
>>> Best regards,
>>> Francois Berenger.
>>>
>>> --
>>> 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
>>>
>>
>> Cheers,
>> Sylvain Le Gall
>
> -- 
> 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
>

Cheers,
Sylvain Le Gall
-- 
Website:     http://sylvain.le-gall.net/
OCaml forge: http://forge.ocamlcore.org
OCaml blogs: http://planet.ocaml.org


  reply	other threads:[~2013-10-01 12:26 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 13:56 [Caml-list] Accelerating compilation Romain Bardou
2013-09-06 14:55 ` Markus Mottl
2013-09-06 15:19   ` Romain Bardou
2013-09-06 15:27     ` Gabriel Scherer
2013-09-06 15:33       ` Alain Frisch
2013-09-06 20:51     ` Fabrice Le Fessant
2013-09-09  7:44       ` Romain Bardou
2013-09-11 13:00       ` Francois Berenger
2013-09-11 13:46         ` Wojciech Meyer
2013-09-12  1:23           ` Francois Berenger
2013-09-12 15:15             ` Jacques Le Normand
2013-09-30  8:06       ` [Caml-list] from oasis to obuild (original subject was Re: Accelerating compilation) Francois Berenger
2013-09-30  8:18         ` Török Edwin
2013-09-30  9:00         ` Fabrice Le Fessant
2013-09-30  9:13           ` Anil Madhavapeddy
2013-09-30 11:13             ` Alain Frisch
2013-09-30 11:19               ` Anil Madhavapeddy
2013-09-30 11:27                 ` Alain Frisch
2013-09-30 11:36                   ` Anil Madhavapeddy
2013-09-30  9:18           ` Francois Berenger
2013-09-30 14:11         ` Sylvain Le Gall
2013-10-01  0:57           ` Francois Berenger
2013-10-01 12:25             ` Sylvain Le Gall [this message]
2013-09-07 11:37     ` [Caml-list] Accelerating compilation Matej Kosik
2013-09-08  6:37     ` Francois Berenger
2013-09-06 15:18 ` Gabriel Scherer
2013-09-06 15:28   ` Romain Bardou
2013-09-06 16:04   ` Markus Mottl
2013-09-06 16:30 ` Xavier Leroy
2013-09-07 19:13   ` Wojciech Meyer
2013-09-07 21:42     ` Jacques-Pascal Deplaix
2013-09-08  1:59       ` Markus Mottl
2013-09-09  7:59   ` Romain Bardou
2013-09-09  8:25   ` Alain Frisch
2013-09-09  8:35     ` Francois Berenger
2013-09-09 10:13     ` Anil Madhavapeddy
2013-09-09 17:08     ` Adrien Nader
2013-09-09 17:17       ` Gabriel Kerneis
2013-09-10  2:01     ` oleg
2013-09-10 10:21       ` Gerd Stolpmann
2013-09-10 16:15       ` Adrien Nader
2013-09-10 16:46       ` Xavier Leroy
2013-09-10 16:53         ` Adrien Nader
2013-09-10 17:43           ` ygrek
2013-09-06 18:45 ` Martin Jambon
2013-09-09  8:15   ` Romain Bardou
2013-09-09  8:36     ` Francois Berenger
2013-09-09  8:41       ` Thomas Refis
2013-09-09 17:32     ` Aleksey Nogin

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=slrnl4lfqn.ntq.sylvain@le-gall.net \
    --to=sylvain@le-gall.net \
    --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