documentation/yocto-project-qs/yocto-project-qs.xml: release name and misc.
I somehow had either dreamed the word "einstein" into the release for 1.1 and had it in there as part of the tarball name, etc. I have replaced this obviously with "edison." Other edits involved making the references to outside documents more consistent. (From yocto-docs rev: 2407b7dd89712c489d515e97d44e3c7dc0b64d20) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
db9d36f196
commit
720446629b
|
@ -36,9 +36,9 @@
|
||||||
<para>
|
<para>
|
||||||
Finally, you might find the Frequently Asked Questions (FAQ) for the Yocto Project
|
Finally, you might find the Frequently Asked Questions (FAQ) for the Yocto Project
|
||||||
at <ulink url='https://wiki.yoctoproject.org/wiki/FAQ'>Yocto Project FAQ</ulink> and
|
at <ulink url='https://wiki.yoctoproject.org/wiki/FAQ'>Yocto Project FAQ</ulink> and
|
||||||
the FAQ appendix located in the
|
the FAQ appendix located in
|
||||||
<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html'>
|
<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html'>
|
||||||
Yocto Project Reference Manual</ulink> helpful.
|
The Yocto Project Reference Manual</ulink> helpful.
|
||||||
</para>
|
</para>
|
||||||
<note>
|
<note>
|
||||||
Due to production processes, there could be differences between the Yocto Project
|
Due to production processes, there could be differences between the Yocto Project
|
||||||
|
@ -316,16 +316,16 @@
|
||||||
through a set of locations.
|
through a set of locations.
|
||||||
If you encounter problems with the Yocto Project finding and downloading source code, see
|
If you encounter problems with the Yocto Project finding and downloading source code, see
|
||||||
the FAQ entry "How does Poky obtain source code and will it work behind my
|
the FAQ entry "How does Poky obtain source code and will it work behind my
|
||||||
firewall or proxy server?" in the
|
firewall or proxy server?" in
|
||||||
<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html'>
|
<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html'>
|
||||||
Yocto Project Reference Manual</ulink>.
|
The Yocto Project Reference Manual</ulink>.
|
||||||
</para></note>
|
</para></note>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ wget http://www.yoctoproject.org/downloads/poky/poky-einstein-6.0.tar.bz2
|
$ wget http://www.yoctoproject.org/downloads/poky/poky-edison-6.0.tar.bz2
|
||||||
$ tar xjf poky-einstein-6.0.tar.bz2
|
$ tar xjf poky-edison-6.0.tar.bz2
|
||||||
$ source poky-einstein-6.0/oe-init-build-env einstein-6.0-build
|
$ source poky-edison-6.0/oe-init-build-env edison-6.0-build
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
@ -333,7 +333,7 @@
|
||||||
To help conserve disk space during builds, you can add the following statement
|
To help conserve disk space during builds, you can add the following statement
|
||||||
to your <filename>local.conf</filename> file in the Yocto Project build
|
to your <filename>local.conf</filename> file in the Yocto Project build
|
||||||
directory, which for this example
|
directory, which for this example
|
||||||
is <filename>einstein-6.0-build</filename>.
|
is <filename>edison-6.0-build</filename>.
|
||||||
Adding this statement deletes the work directory used for building a package
|
Adding this statement deletes the work directory used for building a package
|
||||||
once the package is built.
|
once the package is built.
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
|
@ -349,14 +349,14 @@
|
||||||
<ulink url='http://www.yoctoproject.org'>Yocto Project website</ulink> downloads
|
<ulink url='http://www.yoctoproject.org'>Yocto Project website</ulink> downloads
|
||||||
area to retrieve the tarball.</para></listitem>
|
area to retrieve the tarball.</para></listitem>
|
||||||
<listitem><para>The second command extracts the files from the tarball and places
|
<listitem><para>The second command extracts the files from the tarball and places
|
||||||
them into a directory named <filename>poky-einstein-6.0</filename> in the current
|
them into a directory named <filename>poky-edison-6.0</filename> in the current
|
||||||
directory.
|
directory.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para>The third command runs the Yocto Project environment setup script.
|
<listitem><para>The third command runs the Yocto Project environment setup script.
|
||||||
Running this script defines Yocto Project build environment settings needed to
|
Running this script defines Yocto Project build environment settings needed to
|
||||||
complete the build.
|
complete the build.
|
||||||
The script also creates the Yocto Project
|
The script also creates the Yocto Project
|
||||||
build directory, which is <filename>einstein-6.0-build</filename> in this case.
|
build directory, which is <filename>edison-6.0-build</filename> in this case.
|
||||||
After the script runs, your current working directory is set
|
After the script runs, your current working directory is set
|
||||||
to the build directory.
|
to the build directory.
|
||||||
Later, when the build completes, the build directory contains all the files
|
Later, when the build completes, the build directory contains all the files
|
||||||
|
@ -410,15 +410,16 @@
|
||||||
<filename>core-image-sato</filename> in this example.
|
<filename>core-image-sato</filename> in this example.
|
||||||
For information on the <filename>-k</filename> option use the
|
For information on the <filename>-k</filename> option use the
|
||||||
<filename>bitbake --help</filename> command or see the
|
<filename>bitbake --help</filename> command or see the
|
||||||
"<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#usingpoky-components-bitbake'>BitBake</ulink>" section in the Yocto Project Reference Manual.
|
"<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html#usingpoky-components-bitbake'>BitBake</ulink>" section in
|
||||||
|
<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html'>The Yocto Project Reference Manual</ulink>.
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ bitbake -k core-image-sato
|
$ bitbake -k core-image-sato
|
||||||
</literallayout>
|
</literallayout>
|
||||||
<note><para>
|
<note><para>
|
||||||
BitBake requires Python 2.6 or 2.7. For more information on this requirement,
|
BitBake requires Python 2.6 or 2.7. For more information on this requirement,
|
||||||
see the FAQ appendix in the
|
see the FAQ appendix in
|
||||||
<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html'>
|
<ulink url='http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html'>
|
||||||
Yocto Project Reference Manual</ulink>.
|
The Yocto Project Reference Manual</ulink>.
|
||||||
</para></note>
|
</para></note>
|
||||||
The final command runs the image:
|
The final command runs the image:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
|
|
Loading…
Reference in New Issue