From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 1F411E00576; Tue, 8 Jul 2014 02:55:02 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [147.11.1.11 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 8B4EDE004FF for ; Tue, 8 Jul 2014 02:54:53 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.5) with ESMTP id s689sosB006923 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 8 Jul 2014 02:54:50 -0700 (PDT) Received: from [128.224.162.204] (128.224.162.204) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.3.169.1; Tue, 8 Jul 2014 02:54:50 -0700 Message-ID: <53BBBFE7.3080101@windriver.com> Date: Tue, 8 Jul 2014 17:54:47 +0800 From: Chong Lu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: =?UTF-8?B?Sm9zZXBoIEFuZHJldyBkZSBsYSBQZcOxYQ==?= References: <53BB9D10.30104@windriver.com> In-Reply-To: X-Originating-IP: [128.224.162.204] Cc: "yocto@yoctoproject.org" Subject: Re: QEMU in SDK X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2014 09:55:02 -0000 Content-Type: multipart/alternative; boundary="------------090006000103050908090404" --------------090006000103050908090404 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit I mean you can use adt-installer to make your sdk environment. (3.1.1. Using the ADT Installer) After you run adt-installer script, you can get kernel and rootfs in download_image directory. Best Regards Chong On 07/08/2014 05:39 PM, Joseph Andrew de la Peña wrote: > 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 > 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 >> >> > > --------------090006000103050908090404 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 8bit I mean you can use adt-installer to make your sdk environment. (3.1.1. Using the ADT Installer)
After you run adt-installer script, you can get kernel and rootfs in download_image directory.

Best Regards
Chong


On 07/08/2014 05:39 PM, Joseph Andrew de la Peña wrote:
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





--------------090006000103050908090404--