On Fri, 2021-02-12 at 18:26 +0000, Peter Kjellerstedt wrote: > Since the order of inheriting native/nativesdk is important, rather > than adding warnings about when it is done in the wrong order, which > conflicts with bbappends that want to add inherit statements for > native recipes, wouldn’t it make sense to instead handle this > properly in the code so that native/nativesdk are always inherited > last. An idea to solve this would be to rename native.bbclass and > nativesdk.bbclass to, e.g., native-internal.bbclass and nativesdk- > internal.bbclass, and then make the original classes only set a > special variable (similar to BBCLASSEXTEND), and then later when it > is appropriate check this variable and import the native- > internal/nativesdk-internal class.
We have code to do this properly, it's called BBCLASSEXTEND. It automatically adds the inherit at the end of the recipe. I will also state publicly and clearly than any proposal that involves "-internal" renaming of class files or variables is unlikely to be accepted by me, I have a strong dislike of even the idea of them. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#147991): https://lists.openembedded.org/g/openembedded-core/message/147991 Mute This Topic: https://lists.openembedded.org/mt/80075083/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
