Date
1 - 4 of 4
SSTATE_DIR by MACHINE target?
|
mattwood2000@...
Hi,
is it possible to have SSTATE_DIR overrides based on the MACHINE target or SOC family? For example, is this valid: SSTATE_DIR:sama5 = "/path/to/sstate_a5" SSTATE_DIR:rpi = "/path/to/sstate_rpi" ... Thanks, Matt. |
|
|
|
Quentin Schulz
Hi Matt,
On 1/19/23 17:37, mattwood2000@... wrote: Hi,What are you trying to do? Which problem are you trying to solve that would require this? For example, is this valid:It depends what exactly you want to do, because this would apply only to SSTATE cache for the recipes to build for the target. A Yocto build however is made of native and target recipes. The native recipes are compiled and run on the host, while target recipes are compiled on the host with native binaries from native recipes and run on the target. So native recipes would have their SSTATE cache in a common directory, whether you pick rpi or sama5 as your MACHINE. Cheers, Quentin |
|
|
|
mattwood2000@...
Hi Quentin, I work with many different hardware platforms and architectures. I keep my SSTATE cache on a NAS drive and I was hoping to set up a site.conf that would organize the full build SSTATE cache by architecture. It sounds like this isn't exactly possible. I tried it and the SSTATE directory is still created in the default location in the build directory instead of on my mount point. I guess this is the native SSTATE you are referring to. Thanks, Matt. On Fri, Jan 20, 2023, 7:08 AM Quentin Schulz <quentin.schulz@...> wrote: Hi Matt, |
|
|
|
Quentin Schulz
Hi Matt,
On 1/20/23 14:23, mattwood2000@... wrote: Hi Quentin,Except because of a personal preference of having things spatially separated, it doesn't make much sense to me. When you're building for multiple machines, some sstate-cache is shared. Such is the case of native recipes, but also some target architecture-specific recipes (e.g. something that is built for cortex-a55 cpu, will be reused for all machines based on this cpu). So it actually makes a lot of sense to share as much as possible between all your machines so that your builds are faster, feeding from other machines' builds, and you even save some space on your NAS. I tried it and the SSTATE directory is still created in the defaultYou could have a .conf file specific to each machine and use it. Or also have this SSTATE_DIR variable directly in your machine.conf file. But again, I don't think there's much benefit in doing that :/ Cheers, Quentin |
|
|