Hi Richard and Paul,
> > > We were a little brief on our explanations in the commit message.
> So
> > > we sat down to create a hopefully reproducible demo of the
> problem.
> > >
> > > For reproducing with used core-image-base and local.conf
> containing
> > > the following:
> > >
> > > MACHINE ??= "qemuarm"
> > > USER_CLASSES ?= "buildstats"
> > > PATCHRESOLVE = "noop"
> > > BB_DISKMON_DIRS ??= "\
> > > STOPTASKS,${TMPDIR},1G,100K \
> > > STOPTASKS,${DL_DIR},1G,100K \
> > > STOPTASKS,${SSTATE_DIR},1G,100K \
> > > STOPTASKS,/tmp,100M,100K \
> > > HALT,${TMPDIR},100M,1K \
> > > HALT,${DL_DIR},100M,1K \
> > > HALT,${SSTATE_DIR},100M,1K \
> > > HALT,/tmp,10M,1K"
> > > CONF_VERSION = "2"
> > > DEPENDS:append:pn-base-files = " xorgproto"
> > > RDEPENDS:base-files:append = " xorgproto"
> > > DISTRO_FEATURES:forcevariable = "systemd usrmerge ext2 ipv4 vfat
> > > gobject-instrospection-data ldconfig multiarch"
> > > DISTRO_FEATURES_OPTED_OUT = "*"
> >
> > You're setting RDEPENDS:base-files:append = " xorgproto" and
> xorgproto
> > doesn't exist so it isn't surprising the image generation fails as
> > such. Did you over simplify the reproducer?
>
> You are right, we tried to simply our scenario as much as possible -
> maybe too much.
>
> We are now working on creating an absolute minimum meta-layer, a
> recipe, and an image to reproduce the issue.
>
> The rough sketch is that we will have a foo-program.bb recipe which
> depends on xorgproto. It builds foo.c which uses a constant from a
> xorgproto header file. There will be an image foo-image.bb which
> includes core-image-base and rdepends on foo-program. What then
> happens is that the SDK generated will not contain xorgproto-dev.
>
> What is interesting is that something must have happened between
> Kirkstone and Wrynose: With Kirkstone the above still worked. That is,
> xorgproto-dev was "automatically" part of the SDK. Even without adding
> it to the RDEPENDS.
We created a minimal meta-layer which illustrates the issue we see. You can do
the following to reproduce the issue:
Clone meta-foo
$ git clone https://github.com/rugsi/meta-foo.git
Build SDK for foo-image of meta-foo
$ kas build kas-meta-foo.yml --target foo-image -c populate_sdk
It will build just fine. Nonetheless, the SDK will not contain xorgproto-dev.
$ grep -c xorgproto
build/tmp/deploy/sdk/poky-glibc-x86_64-foo-image-cortexa15t2hf-neon-qemuarm-toolchain-6.0.99+snapshot.target.manifest
0
Once you apply our patch and add RDEPENDS:foo-program = "xorgproto" to
foo-program.bb, the SDK will contain xorgproto-dev.
Our image-foo bases on core-image-base. We did another test basing foo-image on
core-image-sato and adding X11 to the distro features. There, our patch is not
needed and the SDK contains xorgproto-dev. We do not understand why, though. We
think that this is essentially what Paul tested.
We will be on the OSSEU next week. Our email replies could be slower then. But
maybe we can have a chat at the venue.
Cheers,
Mark
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#247117):
https://lists.openembedded.org/g/openembedded-core/message/247117
Mute This Topic: https://lists.openembedded.org/mt/121314987/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
