Good day Chong,

Actually, I have used ADT (Section 3.4 Optionally Building a Toolchain Installer). I used the method -c populate_sdk and it generated a toolchain script from my existing build workdir's core-image-XXX. I ran the toolchain and it generated a sysroots dir to /path/to/sysroots (SDK_PATH).

Here's the directory structure:

+ SDK_PATH

--- + environment-setup-XXX

--- + site-config-XXX

--- + sysroots (dir)

---------- + XXX-poky-linux (dir)

---------- + XXX-pokysdk-linux (dir)

--- + version-XXX

The poky-linux dir does not contain a build dir and nowhere are the images (kernel and ext3) to be found. Thus, the main problem is how can I ran qemu with my SDK setup. This would lead to my sub question: since QEMU needs the kernel and ext3 files, how can I automatically copy these images from my existing build workdir to the newly created SDK dir.

Thanks,

Joseph

On Tue, Jul 8, 2014 at 3:26 PM, Chong Lu <Chong.Lu@windriver.com> wrote:

Hi Joseph,

Maybe you can use adt-installer.

http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-adt-installer

Best Regards
Chong

On 07/08/2014 02:15 PM, Joseph Andrew de la Peña wrote:

Good day ALL,

I was wondering if it's possible to automatically add QEMU dependencies (kernel and ext3 files) into the script generated by do_populate_sdk? Then after running the generated SDK script, the images will reside in /path/to/sysroots/xxx-poky-xxx/tmp/images? Then just add an environment variable to the environment script to locate the images path. Is this possible?

The intention is to run QEMU in a host machine with extracted SDK. Any suggestions on other better ways to run QEMU in another machine w/ SDK would be great.

Thanks,

Joseph