poky/meta-selftest
Paul Barker a1296d40a1 bitbake.conf: Prevent pyc file generation in pseudo context
This also effectively reverts commit b6d30c21b0:
    bitbake.conf: Extend PSEUDO_IGNORE_PATHS to ${COREBASE}/meta

The contents of ${COREBASE}/meta were ignored as pyc files could be
generated for the contents of the lib subdirectory if python modules
were imported within a pseudo context. However this doesn't protect us
from pyc files being generated in the lib directories for other layers.
It's far better to tell python not to produce pyc files when running
under pseudo (by setting the PYTHONDONTWRITEBYTECODE variable) as this
will cover any location where pyc files could possibly be created. This
variable is set in FAKEROOTBASEENV so that it applies to the
bitbake-worker instance for fakeroot tasks, preventing pyc files from
being generated for imports in python tasks themselves.

Also add a test case to ensure that pyc files are not created in tasks
which are executed under pseudo.

(From OE-Core rev: 7aa1ae139b9131faff04c0ed156fd8efcde114f6)

Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 73d538f20743017a44cea4c20dbe09a0327cfc71)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-01-12 14:25:14 +00:00
..
classes
conf layer.conf: Move to gatesgarth naming 2020-05-18 06:33:36 +01:00
files selftest/imagefeatures: add basic test for useradd-staticids 2017-11-08 22:24:03 +00:00
lib bitbake.conf: Prevent pyc file generation in pseudo context 2021-01-12 14:25:14 +00:00
recipes-devtools/python oe-selftest: add some tests for recipeutils module 2018-12-03 12:20:00 +00:00
recipes-test bitbake.conf: Prevent pyc file generation in pseudo context 2021-01-12 14:25:14 +00:00
wic meta/lib/oeqa: Test for bootimg-biosplusefi Source 2019-07-23 22:26:28 +01:00
README

This layer is intended as test layer, used by scripts/oe-selftest
and it's probably a mistake to include it in your builds (unless you
want to run the script).