[yocto] why does quick start guide refer to non-provided "poky-image-sato"?

Joshua Lock josh at linux.intel.com
Thu Jul 14 15:28:51 PDT 2011


On Thu, 2011-07-14 at 18:01 -0400, Robert P. J. Day wrote:
> On Thu, 14 Jul 2011, Rifenbark, Scott M wrote:
> 
> > Robert,
> >
> > My understanding was that the target for this sample command could
> > not be 'core-image-sato' for the QS version on the website, which
> > supports Bernard.  Maybe someone out there has a bit more
> > information on details to your question.
> >
> > ScottR
> >
> > -----Original Message-----
> > From: yocto-bounces at yoctoproject.org [mailto:yocto-bounces at yoctoproject.org] On Behalf Of Robert P. J. Day
> > Sent: Thursday, July 14, 2011 2:32 PM
> > To: Yocto discussion list
> > Subject: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?
> >
> >
> >   maybe i'm misreading something, but the yocto QS guide provides the
> > sample command:
> >
> >   $ bitbake -k poky-image-sato
> >
> > however, nothing provides that target.  i can see the git log entry:
> >
> > commit 1947b17478187bb623da74484747e470ce42d206
> > Author: Scott Rifenbark <scott.m.rifenbark at intel.com>
> > Date:   Tue May 10 12:50:36 2011 -0500
> >
> >     documentation/yocto-project-qs/yocto-project-qs.xml: changed build command
> >
> >     The command used in the example to build an image was using
> >     'bitbake core-image-sato', which is only available in master and
> >     not Bernard.  So, I changed the command to be 'bitbake poky-image-sato'
> >     at Dave Stewart's request.  He located and pointed out the error.
> >
> >     (From yocto-docs rev: 3fa83550aaec5a3549825814a77fa7a823a2daea)
> >
> >     Signed-off-by: Scott Rifenbark <scott.m.rifenbark at intel.com>
> >     Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
> >
> > but it seems that "core-image-sato" is perfectly valid, at least at
> > the moment.  clarification?
> 
>   currently, scripts/oe-setup-builddir lists one of the common targets
> as "core-image-sato", so certainly *something* is out of sync.

As I understand it documentation repository updates are reflected on the
website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.

Joshua
-- 
Joshua Lock
        Yocto Project "Johannes Factotum"
        Intel Open Source Technology Centre




More information about the yocto mailing list