aboutsummaryrefslogtreecommitdiffstats
path: root/oe-init-build-env
diff options
context:
space:
mode:
authorChen Qi <Qi.Chen@windriver.com>2015-08-04 13:54:14 +0800
committerChen Qi <Qi.Chen@windriver.com>2015-08-24 15:40:46 +0800
commit76bc847f69894ced713cda8acf7af0fb72d78a59 (patch)
treecab31dbae7c2b3981701954fb1eeca80ba99d91a /oe-init-build-env
parentcd47fe141d2a0036294838ecb1729a4293453825 (diff)
downloadopenembedded-core-contrib-ChenQi/sdktool.tar.gz
populate_sdk_ext: get rid of buildtoolsChenQi/sdktool
If we do `bitbake buildtools-tarball' and then after one day do `bitbake core-image-minimal -c populate_sdk_ext', we would meet errors like below. | install: cannot stat '/buildarea2/chenqi/poky/build-systemd/tmp/deploy/sdk/ poky-glibc-x86_64-buildtools-tarball-core2-64-buildtools-nativesdk-standalone -1.8+snapshot-20150429.sh': No such file or directory The problem is that the output name for buildtools-tarball has ${DATE} in it. So if populate_sdk_ext task is executed but buildtools-tarball is not rebuilt, the above error appears. In fact, ext SDK does not have to depend on buildtools. This patch removes the buildtools from the ext SDK. After this patch, the ext SDK still works and we can no longer see the buildtools error. [YOCTO #7674] Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Diffstat (limited to 'oe-init-build-env')
0 files changed, 0 insertions, 0 deletions