8491 2015-10-13 06:20:17 +0000 runqemu command is not in the $PATH for toolchain ext sdk 2015-10-16 09:57:15 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 2.0 x86 Multiple RESOLVED WONTFIX Undecided normal --- 1 yi.zhao bluelightning alexandru.c.georgescu ke.zou meta.mr.watcher meta.watcher Qi.Chen randy.e.witt zhangle.yang yi.zhao --- New (Never tested) Don't know oldest_to_newest 55211 0 yi.zhao 2015-10-13 06:20:17 +0000 Git rev: jethro/eac61f37e36099f74485dab398b57f3812826d17 Steps: 1. Build a toolchain ext sdk: bitbake core-image-sato -c populate_sdk_ext 2. Intall the sdk ext: ./poky-glibc-x86_64-core-image-sato-i586-toolchain-ext-2.0.sh 3. Set the environment: $ . /buildarea2/poky_sdk/environment-setup-i586-poky-linux $ which runqemu $ There is no runqemu command in the $PATH, we can not use the toolchain ext to launch pre-build qemu image directly. 55213 1 bluelightning 2015-10-13 06:40:27 +0000 This is semi-intentional. Use "devtool runqemu" instead. 55382 2 bluelightning 2015-10-16 09:57:15 +0000 We have a means to run QEMU within the ext SDK, it just isn't exactly the same as the traditional SDK. We could add a wrapper script fairly easily but I'm just not sure I see a lot of value in doing that, so I'm marking this as WONTFIX. (When the extensible SDK gets documented, which it isn't currently, we will be covering this so user expectations ought to be set correctly.)