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 < [email protected]> wrote: > Hi Matt, > > On 1/19/23 17:37, [email protected] wrote: > > Hi, > > > > is it possible to have SSTATE_DIR overrides based on the MACHINE > > target or SOC family? > > > > What are you trying to do? Which problem are you trying to solve that > would require this? > > > For example, is this valid: > > > > SSTATE_DIR:sama5 = "/path/to/sstate_a5" > > SSTATE_DIR:rpi = "/path/to/sstate_rpi" > > ... > > > > 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 >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59026): https://lists.yoctoproject.org/g/yocto/message/59026 Mute This Topic: https://lists.yoctoproject.org/mt/96380921/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
