summaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2014-11-25 17:58:10 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-12-03 12:23:56 +0000
commitf82156640b1888d5a470db19bed9fc67f198f5ba (patch)
tree58c30a8f933bdea29fc481b2e0c04d3a6e531354 /meta/recipes-extended
parent893f9b21878ef4372331b0e8ab0ca246567830d4 (diff)
downloadpoky-f82156640b1888d5a470db19bed9fc67f198f5ba.tar.gz
gcc: Rework shared work
The current implementation of shared work for gcc is at best confusing. It relies on the fetch/unpack/patch tasks having exactly the same stamps and if this gets broken for some reason, its hard to figure out what the problem is. It also leads to complex code in bitbake. The benefits of shared work for gcc are clear but a better approach is needed. This patch adjusts things so that a single new recipe (gcc-source) provides the fetch/unpack/patch/preconfigure tasks, the rest of gcc simply depends on these tasks and have no fetch/unpack/patch tasks of their own. This means we should get the significant benefits (disk usage/performance) of the single source tree but in a way which has less potential for problems and is easier for people to understand. The cost is an extra recipe/some inc files which is probably a good tradeoff. (From OE-Core rev: ceaa0a448dc5ebddb4f7fb94fb8a503a1c0248c3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended')
0 files changed, 0 insertions, 0 deletions