[yocto] What can I share between projects?

[Darcy Watkins]

Hi,

What about different bblayer.conf stackups?

I was always under impression that as long as you use same layer stack, and the same local.conf (except perhaps switching the MACHINE per build variant), you can share the same tmp directory.  (For example, I could build same project for multiple I.MX6 machines, then for a Layerscape machine, and then for i586 machine).  But once the layer stack changes, you need a different build directory.  (For example some QorIQ SDKs used different layer stacks between ARM and PPC architectures).

And in our case, since we use 'repo' to manage checkouts, as soon as you use different Yocto version branches, you pretty much need a separate checkout, but could share common downloaded content.

Are you saying that the sstate cache is smart enough to handle exact same package for same arch but just built using different layer stack?  (Say one case builds package A with a bbappend, but the other uses a bbappend from a different layer, and say they are at same bbappend revision).

Thanks!



___

Regards,

Darcy

Darcy Watkins ::  Senior Staff Engineer, Firmware

SIERRA WIRELESS
Direct  +1 604 233 7989<tel:+1%20604%20233%207989>   ::  Fax  +1 604 231 1109<tel:+1%20604%20231%201109>  ::  Main  +1 604 231 1100<tel:+1%20604%20231%201100>
13811 Wireless Way  :: Richmond, BC Canada V6V 3A4<x-apple-data-detectors://3/1>
[M4]
dwatkins at sierrawireless.com<mailto:dwatkins at sierrawireless.com> :: www.sierrawireless.com<http://www.sierrawireless.com/> :: www.inmotiontechnology.com<http://www.inmotiontechnology.com/>


On May 20, 2017, at 2:54 AM, Mike Looijmans <mike.looijmans at topic.nl<mailto:mike.looijmans at topic.nl>> wrote:

On 19-05-17 13:47, Mike Looijmans wrote:
On 19-05-17 03:43, Paul D. DeRocco wrote:
If I'm doing multiple unrelated Yocto based projects, and they use the
same version of Yocto, and the same metadata (except for my own layers),
am I right in assuming that I can share everything in poky, downloads, and
sstate-cache, and I only need separate build directories? (I normally put
downloads and sstate-cache next to my build directory, rather than inside
it.)

You can share BOTH the downloads and sstate-cache. You can safely share sstate-cache between various versions of Yocto (OE) and distros, machines, etc., it was designed just for that.
Our build server keeps a single sstate-cache for about 30 projects, with 4 versions of OE, 3 distros, and a dozen MACHINE configs. No problems encountered.

In addition to that, you can share the whole thing ("tmp") for projects that use the same local.conf and the same OE version. Building various images for about 20 different machines with over 4 different architectures (MIPS and ARM variants) in the same directory works just fine and drastically reduces build times since they can share about everything that's not unique to each machine.


Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans at topicproducts.com<mailto:mike.looijmans at topicproducts.com>
Website: www.topicproducts.com<http://www.topicproducts.com>

Please consider the environment before printing this e-mail



Join our presentation at Electronics & Applications 2017:
FPGA for real-time data processing, subject “Hardware platform for industrial ultrasound steel plate Inspection” Topic Embedded Systems - Herman Kuster, 1st June 10 AM

Visit http://eabeurs.nl/author/612884/ for more information

--
_______________________________________________
yocto mailing list
yocto at yoctoproject.org<mailto:yocto at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170520/13d2af1b/attachment.html>