Re: [PATCH] xorgproto: Set ALLOW_EMPTY for the main package

[Paul Barker <paul@pbarker.dev>]

On Fri, 2026-09-18 at 16:18 +0200, mark.jonas@de.bosch.com wrote:
> From: Ricardo Simoes <ricardo.simoes@pt.bosch.com>
> 
> When creating an SDK, the populate_sdk task relies on
> COMPLEMENTARY_GLOB[dev-pkgs] to decide which packages to install [1].
> 
> However, xorgproto is a header-only library, so bitbake does not emit a
> main package. The only reference to the -dev package is an RRECOMMENDS
> from the -dbg package, and such weak links are not honored when
> installing complementary packages [2].
> 
> Fix this by setting ALLOW_EMPTY for the xorgproto package. The main
> package is now emitted, which makes ${PN}-dev reachable through the
> complementary packages and lets recipes that depend on xorgproto be
> built with the SDK.
> 
> [1] https://git.openembedded.org/openembedded-core/tree/meta/classes-recipe/populate_sdk_base.bbclass#n38
> [2] https://docs.yoctoproject.org/ref-manual/variables.html#term-COMPLEMENTARY_GLOB
> 
> Signed-off-by: Ricardo Simoes <ricardo.simoes@pt.bosch.com>
> Signed-off-by: Mark Jonas <mark.jonas@de.bosch.com>
> ---
>  meta/recipes-graphics/xorg-proto/xorgproto_2025.1.bb | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/meta/recipes-graphics/xorg-proto/xorgproto_2025.1.bb b/meta/recipes-graphics/xorg-proto/xorgproto_2025.1.bb
> index e187c56fbc..df09135e27 100644
> --- a/meta/recipes-graphics/xorg-proto/xorgproto_2025.1.bb
> +++ b/meta/recipes-graphics/xorg-proto/xorgproto_2025.1.bb
> @@ -23,3 +23,6 @@ DEV_PKG_DEPENDENCY = ""
>  RRECOMMENDS:${PN}-dbg = "${PN}-dev (= ${EXTENDPKGV})"
>  
>  BBCLASSEXTEND = "native nativesdk"
> +
> +# This is a header only library - thus everything lands in the -dev package
> +ALLOW_EMPTY:${PN} = "1"

Hi Mark, Ricardo,

I built the SDK for core-image-sato, and this already includes
xorgproto-dev without applying this patch. I can see the package listed
in the target manifest and I can see usr/include/X11/X.h in the target
sysroot.

Could you provide a bit more info on the SDK you're building, any local
config changes, etc, so I can reproduce the issue?

Best regards,

-- 
Paul Barker