Re: [yocto] esdk devtool finish workflow

[Adrian Freihofer <adrian.freihofer@gmail.com>]

On Sun, 2024-09-08 at 15:46 +0200, Alexander Kanavin wrote:
> On Sun, 8 Sept 2024 at 15:24, Adrian Freihofer
> <adrian.freihofer@gmail.com> wrote:
> > It is true that we have replaced our eSDK-based setups with Direct
> > SDK-
> > based setups. A year ago, I had the opportunity to talk about this
> > topic at Yocto Sumit: file:///home/adrian/Downloads/yocto-summit-
> > 2023.11-devtool-i_S04eDYy.pdf
> > One year after this presentation, I can summarize that it works
> > much
> > better than what we had with the static eSDK installers.
> 
> You also need to provide a link that can be opened :)

next try :-)
https://summit.yoctoproject.org/media/yocto-project-summit-2023-11/submissions/UZ9BN7/resources/yocto-summit-2023.11-devtool-i_S04eDYy.pdf

> 
> > The second thing you need is a shared sstate-cache. This feature is
> > now
> > available officially in Yocto. We do not use this so far because we
> > do
> > not have a shared hash equivalence server yet. We use a simple, a
> > bit
> > hacky script which downloads all sstate-cache artifacts before we
> > call
> > bitbake.
> 
> You can switch off hash equivalence in local.conf or distro conf or
> site conf. Then sstate signature calculations will work 'as they used
> to', and you can provide only the sstate, without having to set up a
> hashequiv server as well.
> 
> The downside is that it needs to be switched off in CI as well, and
> that can lengthen CI builds significantly, if they no longer benefit
> from hashequiv shortcuts.

Yes, that's how it is. Ideally there would be an easy way to get all
these nice new features together.

> 
> > @Alex: We should discuss this issue in Vienna. I think there has
> > been
> > great progress in many areas. But I don't think there is yet a
> > complete
> > concept for operating a complete infrastructure for distributing
> > layers
> > and ssate-cache, which also provides security and scalability. It's
> > definitely doable with enough knowledge and maybe some helper
> > scripts
> > and compromises as we do it internally or with a CDN without
> > security
> > as the Yocto Project does it.
> 
> We're working on it. You can find the oe-replicate-build prototype
> here:
> https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/sstate-for-all
> (commits 3 to 5 from the top)
> and bitbake-setup prototype here:
> https://github.com/kanavin/bitbake/commits/akanavin/bitbake-setup/
> https://github.com/kanavin/bitbake-setup-configurations
> 
> We should certainly discuss in Vienna, but you can also play with
> these beforehands.

I will have a look at it. It's some time ago when I tried it.

Adrian

> 
> Alex