Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Mikko Rapeli <mikko.rapeli@linaro.org>
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 3/3] systemd: Build the systemctl executable
Date: Wed, 5 Feb 2025 08:06:52 +0100	[thread overview]
Message-ID: <5bc230dd-0480-4a5a-8cac-6137e36538a8@gmail.com> (raw)
In-Reply-To: <Z6ITnblSwyvezrQT@nuoska>

On 04.02.2025 14:18, Mikko Rapeli wrote:
> Hmm, doesn't this overwrite SRC_URI from systemd.inc?
>
> SRC_URI += "file://...patch" would amend the patch file.

Good catch!

>> -S = "${WORKDIR}/sources"
>> -UNPACKDIR = "${S}"
>> -
>> -do_install() {
>> -	install -d ${D}${bindir}
>> -	install -m 0755 ${S}/systemctl ${D}${bindir}
>> -}
>> +MESON_TARGET = "systemctl:executable"
>> +MESON_INSTALL_TAGS = "systemctl"
>> +EXTRA_OEMESON:append = " -Dlink-systemctl-shared=false"
> I wonder why this tag support is needed since MESON_TARGET already
> compiles only the correct executable with static linking. Is it there
> just to let meson handle the install step of a single systemctl
> executable?
>
> Or does it install more files, like config files too?

Correct. It installs much more when no tags specified :)

>
> I'm comparing this to a draft systemd-boot-native recipe for ukify
> which I had and which sets the build target but installs manually:
>
> MESON_TARGET = "ukify"
>
> 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
> }
>
> So the custom do_install() step could be avoided if systemd meson config
> would have "install_tag" for ukify too?

Correct. There's more discussion here 
https://github.com/systemd/systemd/pull/36243 , but if we need more 
tags, they can be added.

>
> Current systemd-boot-native recipe installs/copies the unmodified ukify.py
> from source tree and uses that in native. It doesn't run meson build for it
> and thus things like version details are incorrect. Also some additional tools
> like systemd-measure, systemd-sbsign etc are not compiled so some usecases may
> not be supported atm. If those would also include the install tags, then they
> could be compiled and installed too, I presume.

Yes, that would be an option as well

Slava


  reply	other threads:[~2025-02-05  7:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 10:53 [PATCH v2 1/3] bitbake.conf: Add conditional host tool getent uvv.mail
2025-02-04 10:53 ` [PATCH v2 2/3] meson.bbclass: Add an option to specify install tags uvv.mail
2025-02-04 10:53 ` [PATCH v2 3/3] systemd: Build the systemctl executable uvv.mail
2025-02-04 11:02   ` Patchtest results for " patchtest
2025-02-04 13:18   ` [OE-core] " Mikko Rapeli
2025-02-05  7:06     ` Vyacheslav Yurkov [this message]
2025-02-05  8:30   ` Böszörményi Zoltán
2025-02-04 11:03 ` [OE-core] [PATCH v2 1/3] bitbake.conf: Add conditional host tool getent Richard Purdie
2025-02-04 11:33   ` Vyacheslav Yurkov

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=5bc230dd-0480-4a5a-8cac-6137e36538a8@gmail.com \
    --to=uvv.mail@gmail.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=mikko.rapeli@linaro.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