From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: verifying all necessary OE-related software on your dev host
Date: Tue, 27 Mar 2012 22:40:01 +0100 [thread overview]
Message-ID: <1601708.ZBzUYWUMic@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1203271728430.7513@oneiric>
On Tuesday 27 March 2012 17:33:18 Robert P. J. Day wrote:
> the only thing a beginner might want to do is check that the dev host
> has all essential S/W for OE work. i know that's documented in the
> yocto QS guide here:
>
> http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.h
> tml
>
> is there any automated way to check for this? is there any OE/bitbake
> equivalent to "please check that all necessary commands are
> installed"?
There are checks performed within sanity.bbclass to ensure the availability of
all of these commands, so this happens automatically the first time a build is
run.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-27 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 21:33 verifying all necessary OE-related software on your dev host Robert P. J. Day
2012-03-27 21:37 ` Chris Larson
2012-03-27 21:40 ` Paul Eggleton [this message]
2012-03-27 21:52 ` Robert P. J. Day
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=1601708.ZBzUYWUMic@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox