sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

yocto-project-qs: Final edits for QS manual. 

1. Fixed broken links to the website downloads page.
2. Added a better link to the oe-init-build-env script.
3. Added a note about the image directory because I discovered
   that the QEMU ones have the string "lib32" in prepended
   to them.

(From yocto-docs rev: 38074bc97b94a23b115c44aa9f353205914f7cce)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-04-16 18:02:00 -07:00 committed by Richard Purdie
parent 6cfbc41f72
commit 0478091045
1 changed files with 16 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
documentation/yocto-project-qs/yocto-project-qs.xml
View File

@ -307,11 +307,11 @@
<para> <para>
You can download the latest Yocto Project release by going to the You can download the latest Yocto Project release by going to the
<ulink url="&YOCTO_HOME_URL;/download">Yocto Project Download page</ulink>. <ulink url="&YOCTO_HOME_URL;">Yocto Project website</ulink>
Just go to the page and click the "Yocto Downloads" link found in the "Download" clicking "Downloads" in the navigation pane to the left to view all
navigation pane to the right to view all available Yocto Project releases. available Yocto Project releases.
Then, click the "Yocto Release" link for the release you want from the list to Be sure to scroll down and look for "Yocto Project" under the
begin the download. "Type" heading in the list.
Nightly and developmental builds are also maintained at Nightly and developmental builds are also maintained at
<ulink url="&YOCTO_AB_NIGHTLY_URL;"></ulink>. <ulink url="&YOCTO_AB_NIGHTLY_URL;"></ulink>.
However, for this document a released version of Yocto Project is used. However, for this document a released version of Yocto Project is used.
@ -408,15 +408,16 @@
release tarball from the source repositories using the release tarball from the source repositories using the
<filename>wget</filename> command. <filename>wget</filename> command.
Alternatively, you can go to the Alternatively, you can go to the
<ulink url='&YOCTO_HOME_URL;/download'>Yocto Project website's Downloads page</ulink> <ulink url='&YOCTO_HOME_URL;'>Yocto Project website's</ulink>
to retrieve the tarball.</para></listitem> "Downloads" page 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>&YOCTO_POKY;</filename> in the current them into a directory named <filename>&YOCTO_POKY;</filename> in the current
directory.</para></listitem> directory.</para></listitem>
<listitem><para>The third and fourth commands change the working directory to the <listitem><para>The third and fourth commands change the working directory to the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
and run the Yocto Project and run the Yocto Project
<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'>environment setup script</ulink>. <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
environment setup script.
Running this script defines OpenEmbedded build environment settings needed to Running this script defines OpenEmbedded build environment settings needed to
complete the build. complete the build.
The script also creates the The script also creates the
@ -461,9 +462,9 @@
By default, the OpenEmbedded build system uses the RPM package manager. By default, the OpenEmbedded build system uses the RPM package manager.
You can control this configuration by using the You can control this configuration by using the
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink></filename> variable. <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink></filename> variable.
For additional package manager selection information, see For additional package manager selection information, see the
"<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink>" "<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink>"
in the Yocto Project Reference Manual. section in the Yocto Project Reference Manual.
</para> </para>
<para> <para>
@ -661,6 +662,11 @@
&lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture:
x86, x86-64, ppc, mips, or arm. x86, x86-64, ppc, mips, or arm.
</literallayout> </literallayout>
<note>
For the <filename>qemu</filename> architecture,
<filename>ext3</filename> and <filename>tar</filename>
files start with the "lib32" string.
</note>
</para> </para>
</section> </section>