From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org
Subject: Re: inconsistent pages out there for setting up your yocto dev host
Date: Wed, 21 Nov 2012 22:50:58 +0000 [thread overview]
Message-ID: <2124581.mHRnlHMV84@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1211211718070.14208@oneiric>
On Wednesday 21 November 2012 17:23:56 Robert P. J. Day wrote:
> i've noticed there are various web pages purporting to explain how
> to set up a proper OE/yocto development host, but they give what is
> pretty clearly contradictory information.
>
> as one example, there's this page on getting started with OE:
>
> http://www.openembedded.org/wiki/Getting_started
I produced this page recently; FWIW I also came up with the pared-down package
lists that went into the Quick Start Guide which this page borrows. How is
this contradictory if it uses the same information?
> that claims to steal from a number of sources including the yocto QS
> guide, but look at the packages one is instructed to install on that
> page, particularly under fedora: python, perl, git, and so on.
So I don't recall exactly how perl got on that list; but python and git are
absolutely required on the host. That's why they're in ASSUME_PROVIDED.
> as i read it, the sanity.bbclass and ASSUME_PROVIDED will dictate
> what needs to be there and what will be used if it's installed
> natively, no? it certainly seems that that wiki page is insructing
> the developer to install a lot of software that OE will handle
> automatically, no?
Er, no. Well, if by "handle automatically" you mean "error out when they are
not present" then that's not very helpful - it's much easier if people just
get a list of what they need to install up front.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-11-21 22:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 22:23 inconsistent pages out there for setting up your yocto dev host Robert P. J. Day
2012-11-21 22:50 ` Paul Eggleton [this message]
2012-11-21 23:01 ` Rifenbark, Scott M
2012-11-21 23:45 ` Paul Eggleton
2012-11-22 1:19 ` Robert P. J. Day
2012-11-22 9:56 ` Paul Eggleton
2012-11-22 11:54 ` Robert P. J. Day
2012-11-22 15:35 ` Paul Eggleton
2012-11-23 14:31 ` Robert P. J. Day
2012-11-23 14:39 ` Paul Eggleton
2012-11-23 14:48 ` Robert P. J. Day
2012-11-24 8:03 ` Wolfgang Denk
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=2124581.mHRnlHMV84@helios \
--to=paul.eggleton@linux.intel.com \
--cc=rpjday@crashcourse.ca \
--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.