summaryrefslogtreecommitdiffstats
path: root/meta/conf/bitbake.conf
diff options
context:
space:
mode:
authorRobert Yang <liezhi.yang@windriver.com>2012-03-15 21:50:59 +0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-03-19 20:28:46 +0000
commit5b67d645e33c304119257c59d41645b07df409c4 (patch)
tree24946e1ce0a93059f4956c62adc1da9a1f709f03 /meta/conf/bitbake.conf
parent5bc142ac6c564bfbe3969b4e5717406b6b0406c2 (diff)
downloadpoky-5b67d645e33c304119257c59d41645b07df409c4.tar.gz
native.bbclass: make TOOLCHAIN_OPTIONS empty
The native pkg doesn't need the TOOLCHAIN_OPTIONS, but it maybe used by native pkgs, for example, the cmake.bbclass uses TOOLCHAIN_OPTIONS: OECMAKE_C_FLAGS ?= "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} ${CPPFLAGS}" and TOOLCHAIN_OPTIONS is: TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}" If a native pkg inherits cmake.bbclass, then: TOOLCHAIN_OPTIONS = " --sysroot=" and OECMAKE_C_FLAGS would be: ${HOST_CC_ARCH} --sysroot= ${CPPFLAGS} This would cause unexpected errors, I think that we can make TOOLCHAIN_OPTIONS empty in native.bbclass since native pkg doesn't need it. [YOCTO #2124] (From OE-Core rev: e5555c743a9637f86a0a2c4c45a63a80838e81ae) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/bitbake.conf')
0 files changed, 0 insertions, 0 deletions