Re: [yocto] using shared state cache from other machine
Hi Kurt, On Tue, Jul 7, 2015 at 6:07 AM, Kurt Van Dijck dev.k...@vandijck-laurijssen.be wrote: Hey, 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). The trick to avoid rebuilding all native packages is to rename sstate-cache/Ubuntu-14.04 - sstate-cache/LinuxMint-17.1 after each rsync. Digging around a little in oe-core, it looks like the directory under sstate-cache for native packages is controlled by NATIVELSBSTRING, which is set by lsb_distro_identifier(), which accepts an option adjustment hook via LSB_DISTRO_ADJUST. You can find an example lsb_distro_adjust hook here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor/tree/meta-mel/conf/distro/include/sstate.inc Kind regards, Kurt -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] using shared state cache from other machine
On Tuesday 07 July 2015 14:59:37 Andre McCurdy wrote: On Tue, Jul 7, 2015 at 6:07 AM, Kurt Van Dijck dev.k...@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). 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. 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. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] using shared state cache from other machine
Hey, 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? Kind regards, Kurt -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
