[yocto] fixed: using shared state cache from other machine

Kurt Van Dijck dev.kurt at vandijck-laurijssen.be
Thu Jul 9 01:36:57 PDT 2015


--- Original message ---
> Date: Tue, 07 Jul 2015 23:40:49 +0100
> From: Paul Eggleton <paul.eggleton at linux.intel.com>
> On Tuesday 07 July 2015 14:59:37 Andre McCurdy wrote:
> > On Tue, Jul 7, 2015 at 6:07 AM, Kurt Van Dijck
> > <dev.kurt at vandijck-laurijssen.be> wrote:
> > > I started to re-use the shared state cache from a build machine.
> > > If I clean everything locally, I still spend time building.
> > > So, can everything be re-used, or only the target packages.
> > > How different may the build machine & may host be.
> > > The build machine is a (recent) ubuntu. My machine is debian squeeze+sid
> > > mixed version. Is that a problem?
> > 
> > You can try it, but no guarantees.
> > 
> > I have a build machine running Ubuntu 14.04 and a laptop running Linux
> > Mint 17.1 and I regularly rsync sstate from the build server to the
> > laptop without any issues (as expected, since Linux Mint uses Ubuntu
> > packages). 

I defined the mirror over http, so I skip the rsync.

> 
> The theory is this should work provided the distro you use the native sstate 
> artifacts on has the same or newer glibc version as the one on which they were 
> originally built.

I needed to upgrade locally.

> 
> > The trick to avoid rebuilding all native packages is to
> > rename sstate-cache/Ubuntu-14.04 -> sstate-cache/LinuxMint-17.1 after
> > each rsync.
> 
> Rather than renaming, you can simply create a symlink from the other 
> distribution to the one which was used to do the build.

Due to the http retrieval, I put the symlink on the build server.

Now, I just built a basic image in 10 minutes.
Thank you for the support,
thank you Gigabit ethernet & thank you SSD.

Kind regards,
Kurt



More information about the yocto mailing list