From: Deepak Rathore <[email protected]> Some SDK dependency chains require libyang to be available as host/SDK artifacts. The current metadata only partially provides this, which can lead to dependency resolution failures when this recipe is pulled into SDK-oriented builds.
This change does not alter target package behavior; it only enables required native/nativesdk variants for build and SDK integration paths. Signed-off-by: Deepak Rathore <[email protected]> --- meta-oe/recipes-extended/libyang/libyang_3.13.6.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-oe/recipes-extended/libyang/libyang_3.13.6.bb b/meta-oe/recipes-extended/libyang/libyang_3.13.6.bb index 822c30ba24..122262e73e 100644 --- a/meta-oe/recipes-extended/libyang/libyang_3.13.6.bb +++ b/meta-oe/recipes-extended/libyang/libyang_3.13.6.bb @@ -45,3 +45,4 @@ do_install_ptest () { } FILES:${PN} += "${datadir}/yang/*" +BBCLASSEXTEND += "native nativesdk" -- 2.35.6
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#125226): https://lists.openembedded.org/g/openembedded-devel/message/125226 Mute This Topic: https://lists.openembedded.org/mt/118327827/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
