On Thu, 14 Sept 2023 at 21:54, Richard Purdie <[email protected]> wrote:
> Effectively those "configs" are what the eSDK is, you're just proposing > a server side set of them rather than a built copy. In many ways that > could be useful way of possibly rethinking the way the eSDK works. > > So in that sense I like the idea, we should just be clear the problem > it solves as it doesn't solve the "why is my build not using the cache" > question specifically but it potentially solves other issues. Right, I didn't make it clear that this idea is not about 'why sstate is not being reused', but rather something I thought of to avoid placing people in that situation to begin with - offering them 'pre-fabricated builds' with guaranteed sstate availability. I have a hunch there'll be plenty, for whom this is just fine, and eventually this could be the basis of that oe-setup holy grail :) I'll start with the simplest enhancement of printing what would be rebuilt. There's a lot of code I need to understand, so this needs to be in manageable chunks :) Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1758): https://lists.openembedded.org/g/openembedded-architecture/message/1758 Mute This Topic: https://lists.openembedded.org/mt/101356419/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
