From: "Török Edwin" <edwin+ml-ocaml@etorok.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] from oasis to obuild (original subject was Re: Accelerating compilation)
Date: Mon, 30 Sep 2013 11:18:23 +0300 [thread overview]
Message-ID: <524933CF.4000709@etorok.net> (raw)
In-Reply-To: <5249310F.7090108@riken.jp>
On 09/30/2013 11:06 AM, Francois Berenger wrote:
> On 09/07/2013 05:51 AM, Fabrice Le Fessant wrote:
>> [...]
>> FWIW, I recently compiled Merlin with both ocamlbuild and ocp-build,
>> on a quad-core with "-j 10" for both (the link to the ocp-build
>> description file is in the latest OCamlPro's report), ocamlbuild needs
>> 13s where ocp-build only needs 4s to compile everything.
>
> I recently switched from oasis to obuild.
>
> The main reason I adopted oasis in the past is because the project
> description file (_oasis) is very short.
>
> With ocp-build, (as far as I know) I would have to list all the files
> my program/libraries need to be built, and I am too lazy for that.
>
> But now, I have a project.obuild file instead, which
> is as terse as an _oasis file.
obuild is more like CMake than automake, right? (i.e. it requires itself to be present at build time,
and you can't pregenerate build files)
Best regards,
--Edwin
next prev parent reply other threads:[~2013-09-30 8:18 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 [this message]
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
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=524933CF.4000709@etorok.net \
--to=edwin+ml-ocaml@etorok.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;
as well as URLs for NNTP newsgroup(s).