summaryrefslogtreecommitdiffstats
path: root/meta/classes/pythonnative.bbclass
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2017-04-11 20:38:36 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-04-12 15:09:58 +0100
commit30686e2fd68675bcafd37900ccd00ef8edc96543 (patch)
tree9834bc14d903d8e55501d3e930af9e064267876d /meta/classes/pythonnative.bbclass
parenta9f119382b31a40b600cb574eb896a762259c258 (diff)
downloadpoky-30686e2fd68675bcafd37900ccd00ef8edc96543.tar.gz
go-cross: avoid libgcc dependency
libgcc gets compiled differently depending on the tune flags for the target. That dependency would make go-cross also tune specific and prevent sharing it between different machines using the same architecture. For example, MACHINE=intel-corei7-64 and MACHINE=qemux86-64 shared the same go-cross-x86_64, but compiled libgcc differently. The libgcc dependency gets inherited from go.inc, but does not seem to be necessary for go-cross (compiling go-helloworld still succeeds). The dependency is left in go.inc conditionally, just in case that it really is relevant for the various on-target recipes which inherit that. Because go-cross*.bb includes go*.bb, moving the DEPENDS into a .inc file that only gets included for the target recipes doesn't work. Reshuffling the content of three .bb files seems too intrusive at this point. (From OE-Core rev: 58149a7be4172074349951aaf5af95fa40fd4bdb) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/pythonnative.bbclass')
0 files changed, 0 insertions, 0 deletions