diff options
author | Gyorgy Sarvari <skandigraun@gmail.com> | 2025-02-10 16:45:14 +0100 |
---|---|---|
committer | Khem Raj <raj.khem@gmail.com> | 2025-02-12 09:16:08 -0800 |
commit | 747f2b282b34ccec67062f9bac47a6d4cb4bb274 (patch) | |
tree | b09131bccc0d9b6cc8297d1ebdce5f939623c4e9 /meta-python/recipes-devtools/python/python3-gpiod/0001-bindings-python-tests-disable-device-before-releasin.patch | |
parent | f7aa588db9a0657c00039daee968fd7994c6e111 (diff) | |
download | meta-openembedded-747f2b282b34ccec67062f9bac47a6d4cb4bb274.tar.gz |
mozjs-128: keep persistent state directory in WORKDIR
Mozilla projects (built from Firefox tarball) keep some
content around for the build process, for example Python
virtual environments, which is reused between the tasks.
This folder is by default in $HOME, unless it is overriden
by the MOZBUILD_STATE_PATH environment variable.
Having this content in the $HOME folder can be problematic,
as it can contaminate the build machine. As different
example, when using kas, it creates a new temporary $HOME
with each invokation, which is deleted upon exiting the
kas process. This can fail the build if for example do_compile
and do_install were called in different kas sessions, as the
tools and data stored in this folder are deleted between the
runs.
To solve this, set the MOZBUILD_STATE_PATH environment variable
to a folder inside the $TMPDIR, so this semi-persistent data
can be contained in a known path.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-gpiod/0001-bindings-python-tests-disable-device-before-releasin.patch')
0 files changed, 0 insertions, 0 deletions