From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mikko.rapeli@linaro.org, openembedded-core@lists.openembedded.org
Cc: Erik Schilling <erik.schilling@linaro.org>
Subject: Re: [OE-core] [PATCH 1/3] systemd-tools: add recipe
Date: Mon, 02 Sep 2024 10:59:22 +0100 [thread overview]
Message-ID: <99e13a8ab6cea2424298d97466ad48540cee1209.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240902094117.31156-2-mikko.rapeli@linaro.org>
On Mon, 2024-09-02 at 12:41 +0300, Mikko Rapeli via
lists.openembedded.org wrote:
> From: Erik Schilling <erik.schilling@linaro.org>
>
> Provides systemd-tools-native recipe for ukify.py tooling.
> Avoids full systemd native build which is not needed.
>
> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> ---
> .../systemd/systemd-tools_256.5.bb | 41
> +++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 meta/recipes-core/systemd/systemd-tools_256.5.bb
>
> diff --git a/meta/recipes-core/systemd/systemd-tools_256.5.bb
> b/meta/recipes-core/systemd/systemd-tools_256.5.bb
> new file mode 100644
> index 0000000000..f2e419ffe0
> --- /dev/null
> +++ b/meta/recipes-core/systemd/systemd-tools_256.5.bb
> @@ -0,0 +1,41 @@
> +require systemd.inc
> +FILESEXTRAPATHS =. "${FILE_DIRNAME}/systemd:"
> +
> +DEPENDS = " \
> + intltool-native \
> + libcap \
> + util-linux \
> + gperf-native \
> + python3-jinja2-native \
> + python3-pyelftools-native \
> + python3-pefile \
> +"
> +
> +inherit meson pkgconfig gettext
> +
> +MESON_TARGET = "ukify"
> +
> +# Helper variables to clarify locations. This mirrors the logic in
> systemd's
> +# build system.
> +rootprefix ?= "${root_prefix}"
> +rootlibdir ?= "${base_libdir}"
> +rootlibexecdir = "${rootprefix}/lib"
> +
> +EXTRA_OEMESON += "-Dnobody-user=nobody \
> + -Dnobody-group=nogroup \
> + -Drootlibdir=${rootlibdir} \
> + -Drootprefix=${rootprefix} \
> + -Ddefault-locale=C \
> + -Dmode=release \
> + -Dsystem-alloc-uid-min=101 \
> + -Dsystem-uid-max=999 \
> + -Dsystem-alloc-gid-min=101 \
> + -Dsystem-gid-max=999 \
> +"
> +
> +do_install() {
> + install -d ${D}${bindir}/
> + install -m 0755 ${S}/src/ukify/ukify.py ${D}${bindir}/ukify
> +}
> +
> +BBCLASSEXTEND = "native"
This will fail in CI as there is now maintainers file entry...
Cheers,
Richard
next prev parent reply other threads:[~2024-09-02 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 9:41 [PATCH 0/3] systemd uki support Mikko Rapeli
2024-09-02 9:41 ` [PATCH 1/3] systemd-tools: add recipe Mikko Rapeli
2024-09-02 9:59 ` Richard Purdie [this message]
2024-09-02 10:05 ` [OE-core] " Mikko Rapeli
2024-09-02 10:17 ` Alexander Kanavin
2024-09-02 10:29 ` Mikko Rapeli
2024-09-02 10:36 ` Erik Schilling
2024-09-02 9:41 ` [PATCH 2/3] bitbake.conf: add getopt to HOSTTOOLS Mikko Rapeli
2024-09-02 10:09 ` [OE-core] " Peter Kjellerstedt
2024-09-02 10:15 ` Alexander Kanavin
2024-09-02 10:27 ` Mikko Rapeli
2024-09-02 10:34 ` Alexander Kanavin
[not found] ` <17F1667FB4E21297.30681@lists.openembedded.org>
2024-09-02 10:35 ` Mikko Rapeli
2024-09-02 10:15 ` Mikko Rapeli
2024-09-02 9:41 ` [PATCH 3/3] uki.bbclass: add class for building Unified Kernel Images (UKI) Mikko Rapeli
2024-09-02 10:36 ` Erik Schilling
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=99e13a8ab6cea2424298d97466ad48540cee1209.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=erik.schilling@linaro.org \
--cc=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/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