On Fri, Mar 30, 2012 at 2:54 PM, Chris Larson <clar...@kergoth.com> wrote: > Over the past day, I've implemented a solution for the shared state > reuse issues Mentor has seen with our poky-based product. This > solution is similar in concept to what we had in our Mentor Embedded > Linux 4 (non-yocto-based) product. > > This implementation restructures SSTATE_DIR such that non-target > sstate archives are placed in a directory specific to the host we're > running on, and allows fallback to sstates from compatible hosts. In > addition, there is a hook in place for modifying the returned build > host identifier string. Using these capabilities, configured as you'll > see below at the gist, I can populate sstate-cache from a Centos5 > machine and fully reuse that shared state on a u1004 machine, but if I > take the u1004 sstate-cache and pull it over to Centos5, all the > non-target recipes will be rebuilt.
I forgot to mention, it allows fallback both within the SSTATE_DIR and for mirrors in SSTATE_MIRRORS, as it iterates over each mirror and adjusts the mirror uri to include each compatible host (including the current one). -- Christopher Larson _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core