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

dev-manual: Updated Build Directory term 

The examples went stale.  Two out of three did not work.  I have
provided new examples that work.

Reporte-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: ae50d3ee3c244b2c864d80adf69a7a69fb6e3985)

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-11-11 08:55:53 -08:00 committed by Richard Purdie
parent 8b35d3fdfb
commit 4cab968da8
1 changed files with 28 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
documentation/dev-manual/dev-manual-newbie.xml
View File

@ -514,27 +514,40 @@
The <ulink url='&YOCTO_DOCS_REF_URL;#var-TOPDIR'><filename>TOPDIR</filename></ulink> The <ulink url='&YOCTO_DOCS_REF_URL;#var-TOPDIR'><filename>TOPDIR</filename></ulink>
variable points to the Build Directory.</para> variable points to the Build Directory.</para>
<para>You have a lot of flexibility when creating the Build Directory. <para>
Following are some examples that show how to create the directory: You have a lot of flexibility when creating the Build
Directory.
Following are some examples that show how to create the
directory.
The examples assume your
<link linkend='source-directory'>Source Directory</link> is
named <filename>poky</filename>:
<itemizedlist> <itemizedlist>
<listitem><para>Create the Build Directory in your current working directory <listitem><para>Create the Build Directory inside your
and name it <filename>build</filename>. Source Directory and let the name of the Build
This is the default behavior. Directory default to <filename>build</filename>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ source &OE_INIT_PATH; $ cd $HOME/poky
$ source &OE_INIT_FILE;
</literallayout></para></listitem> </literallayout></para></listitem>
<listitem><para>Provide a directory path and specifically name the build <listitem><para>Create the Build Directory inside your
directory. home directory and specifically name it
This next example creates a Build Directory named <filename>YP-&POKYVERSION;</filename> <filename>test-builds</filename>:
in your home directory within the directory <filename>mybuilds</filename>.
If <filename>mybuilds</filename> does not exist, the directory is created for you:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ source &OE_INIT_PATH; $HOME/mybuilds/YP-&POKYVERSION; $ cd $HOME
$ source poky/&OE_INIT_FILE; test-builds
</literallayout></para></listitem> </literallayout></para></listitem>
<listitem><para>Provide an existing directory to use as the Build Directory <listitem><para>Provide a directory path and
and use the default <filename>build</filename> name. specifically name the build directory.
Any intermediate folders in the pathname must
exist.
This next example creates a Build Directory named
<filename>YP-&POKYVERSION;</filename>
in your home directory within the existing
directory <filename>mybuilds</filename>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ source &OE_INIT_PATH; $HOME/mybuilds/ $cd $HOME
$ source $HOME/poky/&OE_INIT_FILE; $HOME/mybuilds/YP-&POKYVERSION;
</literallayout></para></listitem> </literallayout></para></listitem>
</itemizedlist> </itemizedlist>
</para></listitem> </para></listitem>