From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Navani Srivastava <navani.srivastava@gmail.com>
Cc: yocto@yoctoproject.org,
"navani.srivastava@lnties.com" <navani.srivastava@lnties.com>
Subject: Re: bitbake -c populate_sdk -v poky-image
Date: Thu, 29 Aug 2013 09:13:01 +0100 [thread overview]
Message-ID: <1595398.sI48yF1pnG@helios> (raw)
In-Reply-To: <CA+Z6RkU+5fY9DAz_RCstCj1f_L9PvVEWC1pMaahKjFjjLgkrvQ@mail.gmail.com>
On Thursday 29 August 2013 10:11:31 Navani Srivastava wrote:
> In order to execute
> "bitbake -c populate_sdk poky-image" are we supposed to declare
> BUILD_ARCH or SDK_ARCH somewhere in local.conf file?
> Yocto Documentation has not mentioned anything like that. Just a doubt as
> "bitbake poky-image" is working fine though populate_sdk is giving problem..
You should set SDKMACHINE if you need the machine that runs the SDK to be a
different architecture from the machine that you're running the build on,
otherwise it will just use the same one.
We're aware the documentation is lacking on -c populate_sdk, and we're
addressing that in the documentation for the next release.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-29 8:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 11:03 bitbake -c populate_sdk -v poky-image Navani Srivastava
2013-07-26 15:49 ` Paul Eggleton
2013-07-29 17:59 ` Navani Srivastava
2013-07-29 18:04 ` Paul Eggleton
2013-07-29 18:38 ` Navani Srivastava
2013-07-30 8:27 ` Paul Eggleton
2013-07-30 9:05 ` Navani Srivastava
2013-07-30 10:48 ` Paul Eggleton
2013-07-31 17:14 ` Navani Srivastava
2013-08-28 7:53 ` Navani Srivastava
2013-08-28 14:41 ` Paul Eggleton
2013-08-28 15:13 ` Navani Srivastava
2013-08-29 4:41 ` Navani Srivastava
2013-08-29 8:13 ` Paul Eggleton [this message]
2013-08-29 8:27 ` Navani Srivastava
2013-08-29 8:38 ` Paul Eggleton
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=1595398.sI48yF1pnG@helios \
--to=paul.eggleton@linux.intel.com \
--cc=navani.srivastava@gmail.com \
--cc=navani.srivastava@lnties.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.