summaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended
diff options
context:
space:
mode:
authorPeter Kjellerstedt <peter.kjellerstedt@axis.com>2020-01-07 23:10:42 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-01-28 11:15:02 +0000
commit4fc93977e9ab8d5cf63f383a77610515bd3f032e (patch)
treeb804bcaa82176c0c69795def94c8f53beb945108 /meta/recipes-extended
parentdeb84639381ad6d90893beeb6c5d03f547c07ad9 (diff)
downloadpoky-4fc93977e9ab8d5cf63f383a77610515bd3f032e.tar.gz
sanity.bbclass: Move sanity_info from conf to cache
Since this file is written during recipe parsing, having it in the ${BUILDDIR}/conf directory, which is covered by an inotify watcher, will trigger a re-parse the next time bitbake is run and the resident bitbake server is enabled. This causes the sanity_info file to be updated again, which triggers a new parse the next time bitbake is run ad infinitum. Moving it to ${BUILDDIR}/cache should avoid this. (From OE-Core rev: a63d59f64a2d1f450a7639426cae8e0373a2d764) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit f98103b548aa7dba6b1be6c8e02ef41858a8e85c) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended')
0 files changed, 0 insertions, 0 deletions