From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] qt5webengine: propagate parallel flag to ninja
Date: Sun, 1 Jul 2018 11:05:07 +0200 [thread overview]
Message-ID: <20180701110507.0c0eed41@windsurf.home> (raw)
In-Reply-To: <20180629143521.9018-1-gael.portay@savoirfairelinux.com>
Hello,
On Fri, 29 Jun 2018 10:35:21 -0400, Ga?l PORTAY wrote:
> WebEngine is a big project to build. It uses ninja which is a build
> system that does everything in parallel[1].
>
> Builds are always run in parallel, based by default on the number of
> CPUs your system has. Underspecified build dependencies will result in
> incorrect builds.
>
> QtWebEngine does not propagate the parallel flag from the running
> instance of make to ninja. Thus, all the machine cores are used to build
> this single project.
>
> make -j 10 -> ninja -j # all cores
>
> This behavior disrupts powerful machines which are setup to build many
> projects in parallel. Even worse, the build fails on machines where the
> ratio CPU-cores / amount of RAM (including swap) is not appropriate. g++
> may have not enough of memory to build all those files in parallel.
>
> Unfortunatly, the target `run_ninja' is hardcoded in the Makefile
> src/core/Makefile.run_gn; there is no way to propagate flags using a
> variable through the make command-line.
>
> run_ninja:
> /home/gportay/src/buildroot/output-qt5.11/build/qt5webengine-5.11.1/src/3rdparty/ninja/ninja
> -C /home/gportay/src/buildroot/output-qt5.11/build/qt5webengine-5.11.1/src/core/release QtWebEngineCore
>
> Luckily, the Qt gn_run.pro[2] can hardcode ninja extra flags through the
> variable NINJAFLAGS when the Makefile is generated (which is performed
> during the build and not during configure step).
>
> This commit sets the NINJAFLAGS using the variable PARALLEL_JOBS to limit
> the number of cores used by ninja.
>
> Fixes:
> virtual memory exhausted: Cannot allocate memory
>
> [1]: https://ninja-build.org/manual.html#_comparison_to_make
> [2]: https://github.com/qt/qtwebengine/blob/v5.11.1/src/core/gn_run.pro#L49-L53
>
> CC: Damien Riegel <damien.riegel@savoirfairelinux.com>
> CC: Jean-Fran?ois T?tu <jean-francois.tetu@savoirfairelinux.com>
> Signed-off-by: Ga?l PORTAY <gael.portay@savoirfairelinux.com>
> ---
> Changes since v1:
> - Use PARALLEL_JOBS instead of BR2_JLEVEL
> - Reword commit message
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-07-01 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 14:35 [Buildroot] [PATCH v2] qt5webengine: propagate parallel flag to ninja Gaël PORTAY
2018-06-30 17:07 ` Yann E. MORIN
2018-07-01 9:05 ` Thomas Petazzoni [this message]
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=20180701110507.0c0eed41@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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