On Fri, Sep 8, 2023 at 8:42 AM Yoann Congal <[email protected]> wrote:
> Hi! > Le ven. 8 sept. 2023 à 08:01, MOHAMMED HASSAN <[email protected]> > a écrit : > >> Right, you're not the only one! >> See >> >> https://docs.yoctoproject.org/ref-manual/system-requirements.html#minimum-free-disk-space >> and https://docs.yoctoproject.org/dev/dev-manual/disk-space.html >> >> I can use rm_work and remove all the build related files, however every >> subsequent build would take a lot more time to build. I want my builds to >> be as fast as possible. Do you have any suggestions to for faster builds >> while consuming less memory space. >> > > rm_work does not impact build time. > That's not true, if only do_install task checksum changed, then without rm_work you can reuse existing do_compile and re-run just following tasks, while with rm_work it will need to rebuild from scratch (because do_populate_sysroot and do_package sstate archives won't be valid anymore) adding more wear to those NVME drives. So it's a compromise. > Every important piece of built software is kept in the "sstate cache" and > this cache is not removed by rm_work. > I usually have rm_work activated globally and reasonable build time : most > things are not re-built but taken from the sstate cache. > Depends on what kind of changes you're usually doing and how big your images are. I have it enabled in some builds and disabled in others (and have 8TB NVMEs just for OE builds which are often out of space - but I build a lot of different projects with big images and for multiple different Yocto releases). Cheers,
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60945): https://lists.yoctoproject.org/g/yocto/message/60945 Mute This Topic: https://lists.yoctoproject.org/mt/101231469/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
