The first thing you need to do is set up the OpenEmbedded build environment by sourcing
the <link linkend='structure-core-script'>environment setup script</link> as follows:
<literallayout class='monospaced'>
- $ source &OE_INIT_FILE; [build_dir]
+ $ source &OE_INIT_FILE; [<build_dir>]
</literallayout>
</para>
The <filename>build_dir</filename> is optional and specifies the directory the
OpenEmbedded build system uses for the build -
the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
- If you do not specify a Build Directory it defaults to <filename>build</filename>
+ If you do not specify a Build Directory, it defaults to <filename>build</filename>
in your current working directory.
A common practice is to use a different Build Directory for different targets.
For example, <filename>~/build/x86</filename> for a <filename>qemux86</filename>
target, and <filename>~/build/arm</filename> for a <filename>qemuarm</filename> target.
- See <link linkend="structure-core-script">&OE_INIT_FILE;</link>
- for more information on this script.
+ See the "<link linkend="structure-core-script"><filename>&OE_INIT_FILE;</filename></link>"
+ section for more information on this script.
</para>
<para>
<filename>/meta/recipes-sato/images</filename>, etc. all found in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
Or, the target can be the name of a recipe for a specific piece of software such as
- <application>busybox</application>.
+ BusyBox.
For more details about the images the OpenEmbedded build system supports, see the
"<link linkend="ref-images">Images</link>" chapter.
</para>