All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: "Joseph Andrew de la Peña" <jdelapena@lexmark.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: QEMU in SDK
Date: Tue, 8 Jul 2014 15:26:08 +0800	[thread overview]
Message-ID: <53BB9D10.30104@windriver.com> (raw)
In-Reply-To: <CAJrRHk440JvVsSPcX7PKvbCqLTjz39QQLq1v9OejzRfkyE7iYg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

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
>
>


[-- Attachment #2: Type: text/html, Size: 2378 bytes --]

  reply	other threads:[~2014-07-08  7:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  6:15 QEMU in SDK Joseph Andrew de la Peña
2014-07-08  7:26 ` Chong Lu [this message]
2014-07-08  9:39   ` Joseph Andrew de la Peña
2014-07-08  9:54     ` Chong Lu
2014-07-09  8:27       ` Joseph Andrew de la Peña
2014-07-09  8:53         ` Chong Lu
2014-07-09  9:01           ` Joseph Andrew de la Peña
  -- strict thread matches above, loose matches on Subject: below --
2014-07-08  3:05 Joseph Andrew de la Peña

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53BB9D10.30104@windriver.com \
    --to=chong.lu@windriver.com \
    --cc=jdelapena@lexmark.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.