From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@buildroot.org
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
Pierre Ducroquet <pinaraf@pinaraf.info>,
Samuel Martin <s.martin49@gmail.com>,
Peter Seiderer <ps.report@gmx.net>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH RFC v2 0/7] Use Ninja as build tool for CMake-based packages
Date: Fri, 21 Jan 2022 17:42:28 +0200 [thread overview]
Message-ID: <20220121154235.798255-1-aperez@igalia.com> (raw)
In-Reply-To: <20220112132618.2634250-2-aperez@igalia.com>
Hi all,
Here's a new version of the patch set to use Ninja for all CMake packages.
It is still incomplete (missing documentation, a couple of commits need
better commit logs, etc.) so I will be still using the "RFC" tag =)
This is what I wrote when I sent the initial version:
> In order to avoid the circular dependency of host-ninja requiring itself,
> ninja.mk gets changed to use host-generic-package with a build command
> that plainly runs the compiler on the set of sources we know are needed
> to build a minimal usable version of it under Unix-y systems. This is
> basically the list of sources that CMake would have picked (as per the
> CMakeLists.txt file) passed straight to $(HOSTCXX).
>
> The next change modifies pkg-cmake.mk to always pass -GNinja and removes
> the $(<PKG>_INSTALL[_STAGING,_TARGET]_OPTS) variables, because when using
> Ninja the "install/fast" targets are not generated by CMake (those are
> an internal detail of the Makefile generator, it seems). For consistency
> with the Meson package infrastructure variables $(NINJA), $(<PKG>_NINJA_ENV)
> and $(NINJA_OPTS) are honored by the default set of build/install commands.
While the main changes remain the same, this v2 includes a few fixes for
packages which were needed to make them build using Ninja, and much more
testing: out of the 306 packages which use CMake today, I have been able to
successfully have 205 of them built. I will follow-up with another email
commenting more on this, and with a defconfig attached.
At this point I am confident that we can get all the packages built with
CMake without loss of functionality. Only 5 packages out of 205 needing
minor tweaks is a *very* good sign, IMO.
Cheers,
-Adrian
Adrian Perez de Castro (7):
package/ninja: do not require cmake
package/pkg-cmake.mk: use ninja instead of make
package/musepack: use MUSEPACK_NINJA_OPTS
package/mariadb: use HOST_MARIADB_NINJA_OPTS
package/kf5/kf5-extra-cmake-modules: do not build documentation
package/libcorrect: avoid multiple rules for same target
package/racehound: add patch to support building with ninja
.../kf5-extra-cmake-modules.mk | 5 +
package/libcorrect/libcorrect.mk | 2 +
package/mariadb/mariadb.mk | 2 +-
package/musepack/musepack.mk | 2 +-
package/ninja/ninja.mk | 36 +++++-
package/pkg-cmake.mk | 24 ++--
...pport-non-Make-generators-e.g.-Ninja.patch | 112 ++++++++++++++++++
7 files changed, 170 insertions(+), 13 deletions(-)
create mode 100644 package/racehound/0002-CMake-Support-non-Make-generators-e.g.-Ninja.patch
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-21 15:43 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 ` Adrian Perez de Castro [this message]
2022-01-21 15:42 ` [Buildroot] [PATCH RFC v2 1/7] " 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
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=20220121154235.798255-1-aperez@igalia.com \
--to=aperez@igalia.com \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=pinaraf@pinaraf.info \
--cc=ps.report@gmx.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox