public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Alexander Kanavin <alex.kanavin@gmail.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] systemd: Allow native build
Date: Tue, 4 Apr 2023 10:31:16 +0200	[thread overview]
Message-ID: <a465afbf-b085-b02d-b0a8-3cc9b4f7f9ee@gmail.com> (raw)
In-Reply-To: <3C4EAC0F-C717-4FFC-9885-808BAB334616@arm.com>

2023. 04. 03. 21:52 keltezéssel, Ross Burton írta:
>
>> On 3 Apr 2023, at 14:00, Böszörményi Zoltán <zboszor@gmail.com> wrote:
>>
>> 2023. 04. 03. 12:59 keltezéssel, Ross Burton írta:
>>> On 31 Mar 2023, at 10:46, Zoltan Boszormenyi via lists.openembedded.org <zboszor=gmail.com@lists.openembedded.org> wrote:
>>>> Regarding my attempts to fix this: I have looked into
>>>> making these executables use "native: true" but it
>>>> would need duplicating all the driver and library targets
>>>> with "native: true", too, and it seemed to be too intrusive.
>>>> Also, it doesn't eliminate the native dependency chain,
>>>> building these executables would still need systemd-native,
>>>> libgudev-native and libgusb-native.
>>> I’d say this is still the correct solution, although the ‘native’ libfprint would be as lean as possible and not the entire library.
>> Hopefully someone can solve this bug soon:
>> https://github.com/mesonbuild/meson/issues/11029
>> FWIW, I commented about the problem but the meson
>> codebase is over my head so I can't fix it.
>>
>> Then libfrint (and probably other meson bases recipes
>> in Yocto) won't need a native part.
> FWIW I just took a stripped down copy of your libfprint recipe and it happily built using qemu’s exe wrapper in oe-core master.

After a fresh "repo sync" my libfprint build still fails with the
stripped down copy that doesn't want the native dependency.

Please share the changes of yours against the libfprint recipe
because clearly I am doing something wrong which is not
obvious to me.

Or there is something subtle going on. For example, does
this stripped down copy of the libfprint recipe still build
for you if meta-clang is also used?

> So, yes, it would be good if the build used native instead of relying on qemu, but it’s not a hard blocker.  We should definitely be doing AB runs of poky with the exe wrapper disabled to exercise those codepaths.
>
> Ross



      reply	other threads:[~2023-04-04  8:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 13:42 [PATCH 1/2] systemd: Allow native build Zoltán Böszörményi
2023-03-30 13:42 ` [PATCH 2/2] libgudev: " Zoltán Böszörményi
2023-03-30 13:47   ` [OE-core] " Alexander Kanavin
2023-03-30 14:01     ` Böszörményi Zoltán
2023-03-30 13:46 ` [OE-core] [PATCH 1/2] systemd: " Alexander Kanavin
2023-03-30 14:04   ` Böszörményi Zoltán
2023-03-30 13:50 ` Richard Purdie
2023-03-30 14:08   ` Böszörményi Zoltán
2023-03-30 14:10     ` Alexander Kanavin
2023-03-30 14:31       ` Böszörményi Zoltán
2023-03-30 14:41         ` Alexander Kanavin
2023-03-30 14:51           ` Böszörményi Zoltán
2023-03-30 14:57             ` Alexander Kanavin
     [not found]       ` <175138E3E9EE1FF1.27612@lists.openembedded.org>
2023-03-30 14:45         ` Böszörményi Zoltán
2023-03-30 16:39       ` Richard Purdie
2023-03-31  9:39         ` Böszörményi Zoltán
     [not found]         ` <1751778F66ADC2DD.27612@lists.openembedded.org>
2023-03-31  9:46           ` Böszörményi Zoltán
2023-04-03 10:59             ` Ross Burton
2023-04-03 13:00               ` Böszörményi Zoltán
2023-04-03 19:52                 ` Ross Burton
2023-04-04  8:31                   ` Böszörményi Zoltán [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=a465afbf-b085-b02d-b0a8-3cc9b4f7f9ee@gmail.com \
    --to=zboszor@gmail.com \
    --cc=Ross.Burton@arm.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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