From: Malcolm Matalka <mmatalka@gmail.com>
To: Francois Berenger <berenger@riken.jp>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] which ocaml build system
Date: Fri, 26 Jul 2013 07:01:07 +0200 [thread overview]
Message-ID: <CAKziXDXz7Ev9HPaoAaGK_DsLuaJZFtJkrMv0203Uofbmys5Aaw@mail.gmail.com> (raw)
In-Reply-To: <51F1CC76.60802@riken.jp>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
make -j<number > should work.
On Jul 26, 2013 3:10 AM, "Francois Berenger" <berenger@riken.jp> wrote:
> On 07/26/2013 06:45 AM, Martin DeMello wrote:
>
>> On Tue, Jul 23, 2013 at 6:39 AM, Marek Kubica <marek@xivilization.net>
>> wrote:
>>
>>>
>>> I would like to gather thoughts on that in the ocaml.org website,
>>>> because actually its advice is 'make + OcamlMakefile' and 'Omake',
>>>> and I am not sure it is the best advice.
>>>>
>>>
>>> I suppose this advice used to be good, but today maybe not as much
>>> anymore.
>>>
>>
>> I have an old (and fairly small) project that I've tried at least
>> thrice to migrate off OcamlMakefile to something more
>> modern/ocaml-specific, and failed each time (after spending 1-2
>> evenings on it). I'll give it another go and report back on my
>> experience, but at least historically OCamlMakefile was the easiest
>> thing to get up and running.
>>
> >
>
>> You can see the pretty simple makefile here:
>> https://github.com/**martindemello/varix/blob/**master/makefile<https://github.com/martindemello/varix/blob/master/makefile>- I can't
>> remember exactly what difficulties I had with ocamlbuild and omake
>> now.
>>
>
> How is the parallelization of the build with OCamlMakefile?
>
> Is it good (i.e. faster than ocamlbuild)?
>
> F.
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/**arc/caml-list<https://sympa.inria.fr/sympa/arc/caml-list>
> Beginner's list: http://groups.yahoo.com/group/**ocaml_beginners<http://groups.yahoo.com/group/ocaml_beginners>
> Bug reports: http://caml.inria.fr/bin/caml-**bugs<http://caml.inria.fr/bin/caml-bugs>
>
[-- Attachment #2: Type: text/html, Size: 2727 bytes --]
next prev parent reply other threads:[~2013-07-26 5:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51ECF4EB.1060301@libertysurf.fr>
2013-07-22 9:07 ` r.3
2013-07-22 15:11 ` Ashish Agarwal
2013-07-23 13:39 ` Marek Kubica
2013-07-25 21:45 ` Martin DeMello
2013-07-26 1:10 ` Francois Berenger
2013-07-26 5:01 ` Malcolm Matalka [this message]
2013-07-26 5:46 ` Adrien Nader
2013-07-26 6:49 ` rixed
2013-07-26 7:07 ` David Allsopp
2013-07-26 4:49 ` Gabriel Scherer
2013-08-05 17:34 ` [Caml-list] character syntax error '^M' r.3
2013-08-05 17:38 ` David Allsopp
2013-08-05 20:23 ` William R
2013-08-06 10:52 ` David Allsopp
2013-07-27 9:51 ` [Caml-list] which ocaml build system Goswin von Brederlow
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=CAKziXDXz7Ev9HPaoAaGK_DsLuaJZFtJkrMv0203Uofbmys5Aaw@mail.gmail.com \
--to=mmatalka@gmail.com \
--cc=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).