On Fri, 26 Jun 2026 at 16:55, Luca Fancellu <[email protected]> wrote: > On the production usage: I cannot point to a public OpenEmbedded/Yocto layer > today. The concrete use case that triggered this work is not public yet, and I > am not aware of another public layer consuming LLVM MLIR at the moment, so I > do > not want to overstate that part. > > I still think oe-core is the right place for this because it is an optional, > standalone recipe for a component from the same llvm-project source tree that > oe-core already provides. If the lack of a public production consumer makes it > premature, I can hold the patch back until such a consumer is available. > Otherwise I will send a v2 with the expanded commit message and selftest > coverage.
You should send a v2, so it gets a full review. Whether oe-core should carry something that technically belongs in oe-core, but has no open source consumers is a question for the openembedded technical steering committee. My personal take (and I'm not in the TSC) is that the situation is fundamentally unfair: this pushes the maintenance burden onto the openembedded community (for example, when this recipe fails to build or fails to pass its test on clang version bump or other changes), while the benefits are kept to this proprietary, secretive project that you're involved in. If/when there's a public consumer, this would tilt the balance clearly in favour. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#239652): https://lists.openembedded.org/g/openembedded-core/message/239652 Mute This Topic: https://lists.openembedded.org/mt/119973309/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
