summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/libsoup
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2022-01-31 15:44:56 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-02-05 12:26:36 +0000
commit12118f74efd53ffd3d3e6b95b2fc1763dcaebd57 (patch)
tree9d4c880cac61f7c68895eac3d0cb13a87fe16bd5 /meta/recipes-support/libsoup
parent2d055b787a59dab30beb4537fcf5504abec47a3a (diff)
downloadpoky-12118f74efd53ffd3d3e6b95b2fc1763dcaebd57.tar.gz
staging: Add extra hash handling code
Target build output, stored in do_populate_sysroot or do_package can depend not only upon direct dependencies but also indirect ones. A good example is linux-libc-headers. The toolchain depends on this but most target recipes do not. There are some headers which are not used by the toolchain build and do not change the toolchain task output, hence the task hashes can change without changing the sysroot output of that recipe yet they can influence others. A specific example is rtc.h which can change rtcwake.c in util-linux but is not used in the glibc or gcc build. To account for this, we need to account for the populate_sysroot hashes in the task output hashes. (From OE-Core rev: 1cf62882bbac543960e4815d117ffce0e53bda07) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-support/libsoup')
0 files changed, 0 insertions, 0 deletions