From: James Hilliard <james.hilliard1@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
Samuel Martin <s.martin49@gmail.com>,
Alexander Dahl <post@lespocky.de>,
buildroot <buildroot@buildroot.org>,
Adrian Perez de Castro <aperez@igalia.com>
Subject: Re: [Buildroot] [PATCH RFC 0/2] Use Ninja as build tool for CMake-based packages
Date: Thu, 5 May 2022 15:35:45 -0600 [thread overview]
Message-ID: <CADvTj4pYst3nWE4aA_LAvrZYjhVP+XL3RwpdjBfGgHA9w7qEJw@mail.gmail.com> (raw)
In-Reply-To: <20220113164906.5db00b20@windsurf>
On Thu, Jan 13, 2022 at 8:49 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> On Wed, 12 Jan 2022 19:55:03 +0100
> Arnout Vandecappelle <arnout@mind.be> wrote:
>
> > There's one disadvantage to Ninja in Buildroot context: until [1] is fixed, it
> > doesn't collaborate well with top-level parallel build. This means that if you
> > run with a toplevel JLEVEL of e.g. 24, you can easil end up with 40-100 compiles
> > running in parallel. The problem already exists for meson packages, but these
> > are sufficiently rare that they don't pose a problem in practice. I don't know
> > if it's going to become a problem if cmake packages are added to the mix.
>
> meson-based packages are no longer rare: we now have 116 packages using
> the meson-package infrastructure, including very high profile packages
> such as systemd, mesa3d, libglib2, and more.
>
> It is still higher than the 328 cmake-based package we have of course,
> but I wouldn't say that meson is "sufficiently rare" :-)
>
> Annoying that this problem hasn't been resolved in upstream ninja :-/
We're now using kitware/cmake's fork with jobserver support FYI:
https://github.com/buildroot/buildroot/commit/227d7e0cbaaf093f509f5728f06fad5f53caed7b
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-05 21:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 13:26 [Buildroot] [PATCH RFC 0/2] Use Ninja as build tool for CMake-based packages Adrian Perez de Castro
2022-01-12 13:26 ` [Buildroot] [PATCH RFC 1/2] package/ninja: do not require cmake Adrian Perez de Castro
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 0/7] Use Ninja as build tool for CMake-based packages Adrian Perez de Castro
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 1/7] package/ninja: do not require cmake Adrian Perez de Castro
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 2/7] package/pkg-cmake.mk: use ninja instead of make Adrian Perez de Castro
2022-07-24 13:16 ` Arnout Vandecappelle
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 3/7] package/musepack: use MUSEPACK_NINJA_OPTS Adrian Perez de Castro
2022-07-24 13:18 ` Arnout Vandecappelle
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 4/7] package/mariadb: use HOST_MARIADB_NINJA_OPTS Adrian Perez de Castro
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 5/7] package/kf5/kf5-extra-cmake-modules: do not build documentation Adrian Perez de Castro
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 6/7] package/libcorrect: avoid multiple rules for same target Adrian Perez de Castro
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 7/7] package/racehound: add patch to support building with ninja Adrian Perez de Castro
2022-01-21 15:53 ` [Buildroot] [PATCH RFC v2 0/7] Use Ninja as build tool for CMake-based packages Adrian Perez de Castro
2022-01-12 13:26 ` [Buildroot] [PATCH RFC 2/2] package/pkg-cmake.mk: use ninja instead of make Adrian Perez de Castro
2022-01-12 14:35 ` Thomas Petazzoni
2022-01-12 16:51 ` Adrian Perez de Castro
2022-01-12 14:36 ` [Buildroot] [PATCH RFC 0/2] Use Ninja as build tool for CMake-based packages Thomas Petazzoni
2022-01-12 15:09 ` Adrian Perez de Castro
2022-01-12 16:02 ` Thomas Petazzoni
2022-01-12 16:05 ` Alexander Dahl
2022-01-12 16:47 ` Adrian Perez de Castro
2022-01-12 18:55 ` Arnout Vandecappelle
2022-01-13 15:49 ` Thomas Petazzoni
2022-05-05 21:35 ` James Hilliard [this message]
2022-07-24 13:05 ` Arnout Vandecappelle
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=CADvTj4pYst3nWE4aA_LAvrZYjhVP+XL3RwpdjBfGgHA9w7qEJw@mail.gmail.com \
--to=james.hilliard1@gmail.com \
--cc=aperez@igalia.com \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=post@lespocky.de \
--cc=s.martin49@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.