aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml26
1 files changed, 16 insertions, 10 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 6825e2cfe9..352f89e04f 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -307,11 +307,11 @@
<para>
You can download the latest Yocto Project release by going to the
- <ulink url="&YOCTO_HOME_URL;/download">Yocto Project Download page</ulink>.
- Just go to the page and click the "Yocto Downloads" link found in the "Download"
- navigation pane to the right to view all available Yocto Project releases.
- Then, click the "Yocto Release" link for the release you want from the list to
- begin the download.
+ <ulink url="&YOCTO_HOME_URL;">Yocto Project website</ulink>
+ clicking "Downloads" in the navigation pane to the left to view all
+ available Yocto Project releases.
+ Be sure to scroll down and look for "Yocto Project" under the
+ "Type" heading in the list.
Nightly and developmental builds are also maintained at
<ulink url="&YOCTO_AB_NIGHTLY_URL;"></ulink>.
However, for this document a released version of Yocto Project is used.
@@ -408,15 +408,16 @@
release tarball from the source repositories using the
<filename>wget</filename> command.
Alternatively, you can go to the
- <ulink url='&YOCTO_HOME_URL;/download'>Yocto Project website's Downloads page</ulink>
- to retrieve the tarball.</para></listitem>
+ <ulink url='&YOCTO_HOME_URL;'>Yocto Project website's</ulink>
+ "Downloads" page to retrieve the tarball.</para></listitem>
<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
directory.</para></listitem>
<listitem><para>The third and fourth commands change the working directory to the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
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
complete the build.
The script also creates the
@@ -461,9 +462,9 @@
By default, the OpenEmbedded build system uses the RPM package manager.
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.
- 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>"
- in the Yocto Project Reference Manual.
+ section in the Yocto Project Reference Manual.
</para>
<para>
@@ -661,6 +662,11 @@
&lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture:
x86, x86-64, ppc, mips, or arm.
</literallayout>
+ <note>
+ For the <filename>qemu</filename> architecture,
+ <filename>ext3</filename> and <filename>tar</filename>
+ files start with the "lib32" string.
+ </note>
</para>
</section>