MIME-Version: 1.0
References: <BYZDB5LH4OVY.9FDVF5I3J954@homura> <20191211094116.4908c616@ncopa-desktop.copa.dup.pw>
In-Reply-To: <20191211094116.4908c616@ncopa-desktop.copa.dup.pw>
From: Kiyoshi Aman <aphrael@alpinelinux.org>
Date: Wed, 11 Dec 2019 08:58:44 -0500
Message-ID: <CAML-Udta6PjdKJEAYvee6rvOxRi-ywYB7Uj5nDkp9K0fM1FZzA@mail.gmail.com>
Subject: Re: Proposal: replace ninja with samurai
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: Drew DeVault <sir@cmpwn.com>, ~alpine/devel@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"

On Wed, Dec 11, 2019 at 3:41 AM Natanael Copa <ncopa@alpinelinux.org> wrote:
>
> On Sat, 07 Dec 2019 12:37:56 -0500
> "Drew DeVault" <sir@cmpwn.com> wrote:
>
> > Ninja is a build tool which fills the same niche as Make, and samurai is
> > a third-party implementation on of Ninja.
> >
> > https://github.com/ninja-build/ninja
> > https://github.com/michaelforney/samurai
> >
> > samu is much simpler than ninja, clocking in at around ~3,000 lines of
> > C, compared to Ninja's ~20,000 lines of C++. samu also supports a
> > SAMUFLAGS environment variable which we can use to tune the -j flag in
> > abuild, similar to Make. Samurai is a drop-in replacement, but is not
> > bug-for-bug compatible with Ninja.
>
> What I think is nice with ninja compared to make, is that we don't need
> set -j to make it use all cores. Will samurai not use all detected
> cores without setting -j?

The primary reason to include -j$JOBS is not because samurai won't use
all cores by default, but rather because, in some circumstances, using
all cores may not be desirable (e.g. if one lacks the RAM to utilize
all available cores at once on large projects).