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

documentation: yocto-project-qs - Final changes before the 1.3 lockdown 

Fixed used of "Source Directory" and Build Directory.

(From yocto-docs rev: a4d79c5a7e73003fc99c274d876fbea453a80d20)

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 2012-10-22 14:22:09 -07:00 committed by Richard Purdie
parent a73fde8caf
commit 60a26d2496
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -56,7 +56,7 @@
<listitem><para><emphasis>FAQs:</emphasis> Lists commonly asked Yocto Project questions and answers. <listitem><para><emphasis>FAQs:</emphasis> Lists commonly asked Yocto Project questions and answers.
You can find two FAQs: <ulink url='&YOCTO_WIKI_URL;/wiki/FAQ'>Yocto Project FAQ</ulink> on You can find two FAQs: <ulink url='&YOCTO_WIKI_URL;/wiki/FAQ'>Yocto Project FAQ</ulink> on
a wiki, and the a wiki, and the
<ulink url='&YOCTO_DOCS_REF_URL;#faq'>FAQ</ulink> chapter in "<ulink url='&YOCTO_DOCS_REF_URL;#faq'>FAQ</ulink>" chapter in
the Yocto Project Reference Manual. the Yocto Project Reference Manual.
</para></listitem> </para></listitem>
<listitem><para><emphasis>Developer Screencast:</emphasis> The <listitem><para><emphasis>Developer Screencast:</emphasis> The
@ -406,23 +406,23 @@
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 environment setup script. and run the Yocto Project 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
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>, <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>,
which is <filename>build</filename> in this case and is located in the which is <filename>build</filename> in this case and is located in the
source directory. Source Directory.
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
created during the build. created during the build.
</para></listitem> </para></listitem>
</itemizedlist> </itemizedlist>
<para> <para>
Take some time to examine your <filename>local.conf</filename> file Take some time to examine your <filename>local.conf</filename> file
in your project's configuration directory, which is found in the build directory. in your project's configuration directory, which is found in the Build Directory.
The defaults in that file should work fine. The defaults in that file should work fine.
However, there are some variables of interest at which you might look. However, there are some variables of interest at which you might look.
</para> </para>
@ -741,7 +741,7 @@
<title>Getting the Yocto Project</title> <title>Getting the Yocto Project</title>
<para> <para>
Set up your <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink> Set up your <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
one of two ways: one of two ways:
<itemizedlist> <itemizedlist>
<listitem><para><emphasis>Tarball:</emphasis> <listitem><para><emphasis>Tarball:</emphasis>
@ -775,9 +775,9 @@
<para> <para>
From the parent directory your From the parent directory your
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>, <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
initialize your environment and provide a meaningful initialize your environment and provide a meaningful
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink> <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
name: name:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ source poky/&OE_INIT_FILE; mybuilds $ source poky/&OE_INIT_FILE; mybuilds
@ -785,7 +785,7 @@
At this point, the <filename>mybuilds</filename> directory has been created for you At this point, the <filename>mybuilds</filename> directory has been created for you
and it is now your current working directory. and it is now your current working directory.
If you don't provide your own directory name it defaults to <filename>build</filename>, If you don't provide your own directory name it defaults to <filename>build</filename>,
which is inside the source directory. which is inside the Source Directory.
</para> </para>
</section> </section>
@ -794,7 +794,7 @@
<para> <para>
Initializing the build environment creates a <filename>conf/local.conf</filename> configuration file Initializing the build environment creates a <filename>conf/local.conf</filename> configuration file
in the build directory. in the Build Directory.
You need to manually edit this file to specify the machine you are building and to optimize You need to manually edit this file to specify the machine you are building and to optimize
your build time. your build time.
Here are the minimal changes to make: Here are the minimal changes to make: