From: Markus Volk <f_l_k@t-online.de>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe
Date: Fri, 20 May 2022 14:46:47 +0200 [thread overview]
Message-ID: <70887c7d-4063-93d5-025f-46c4a17e5940@t-online.de> (raw)
In-Reply-To: <20220519184315.1e91b017@melee>
i have started here locally to resolve all dependencies to be able to
build pipewire-native. Besides I tried to untie the node when building
libpam-native, because otherwise I can't compile openssh-native either.
All in all, the changes were more invasive than I had hoped. Quite some
recipes needed to be added for native and I'm not sure if anything got
broken in the process. In any case, RFC. Test-wise, I ran -c
populate_sdk for my full image with about 13500 tasks. I had a problem
with nativesdk-cairo and had to disable a runtime test. But that was
related to the meson buildsystem. On the bright side, I otherwise had no
issues with building nativesdk and the changes also solved some of my
problems. nativesdk-libdecor-dev was created just fine here.
Since this is all very experimental and even unsure if this should end
up in core, editing the maintainer for libdecor still has time. For
libusb1 I added a PACKAGECONFIG option and a comment what you want to
enable it for. I'll send an updated patchset because it might be
interesting for some to experiment with it.
I also had to make some changes in meta-openembedded. I send these
patches to openembedded-devel
Markus
Am 19.05.22 um 18:43 schrieb Luca Ceresoli:
> And also this warning:
>
> WARNING: Nothing RPROVIDES 'nativesdk-libdecor' (but
> virtual:nativesdk:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-graphics/libdecor/libdecor_0.1.0.bb
> RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for
> 'nativesdk-libdecor' NOTE: Runtime target 'nativesdk-libdecor' is
> unbuildable, removing... Missing or unbuildable dependency chain was:
> ['nativesdk-libdecor'] WARNING: Nothing RPROVIDES
> 'nativesdk-libdecor-dev' (but
> virtual:nativesdk:/home/pokybuild/yocto-worker/build-appliance/build/meta/recipes-graphics/libdecor/libdecor_0.1.0.bb
> RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for
> 'nativesdk-libdecor-dev' NOTE: Runtime target 'nativesdk-libdecor-dev'
> is unbuildable, removing... Missing or unbuildable dependency chain
> was: ['nativesdk-libdecor-dev']
next prev parent reply other threads:[~2022-05-20 12:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 6:43 [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe Markus Volk
2022-05-19 6:43 ` [meta-oe][RFC PATCH 2/2] libsdl2: rework and cleanup Markus Volk
2022-05-19 14:18 ` [OE-core] " Luca Ceresoli
2022-05-19 14:30 ` Markus Volk
2022-05-19 15:15 ` Alexander Kanavin
2022-05-19 16:43 ` [OE-core] [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe Luca Ceresoli
2022-05-19 16:46 ` Alexander Kanavin
2022-05-19 19:42 ` Markus Volk
2022-05-19 19:59 ` Alexander Kanavin
2022-05-19 20:12 ` Markus Volk
2022-05-20 12:46 ` Markus Volk [this message]
2022-05-21 7:48 ` richard.purdie
2022-05-22 8:48 ` Markus Volk
2022-05-22 9:24 ` richard.purdie
2022-05-22 10:22 ` Markus Volk
2022-05-22 12:12 ` richard.purdie
2022-05-22 17:26 ` Markus Volk
2022-05-23 15:26 ` Markus Volk
2022-05-31 19:06 ` Markus Volk
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=70887c7d-4063-93d5-025f-46c4a17e5940@t-online.de \
--to=f_l_k@t-online.de \
--cc=luca.ceresoli@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.