diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-09-18 10:36:16 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-09-22 12:20:48 +0100 |
commit | 26354c27151a1053a69a669f7ebf6a5ed46735f9 (patch) | |
tree | abb5dad8e649dec82621949932bc9b9ecebf75d6 /documentation/ref-manual/closer-look.xml | |
parent | 33ed042d4f6de99efca7c6724b8966b9da79e330 (diff) | |
download | ast2050-yocto-poky-26354c27151a1053a69a669f7ebf6a5ed46735f9.zip ast2050-yocto-poky-26354c27151a1053a69a669f7ebf6a5ed46735f9.tar.gz |
ref-manual, mega-manual: Updates to "Image Generation"
Fixes [YOCTO #2808]
Updated the figure and placed it in the folders area for both
the ref-manual and mega-manual. I had to add the
DEPLOY_DIR_IMAGE variable and create a new machine-specific
directory below deploy. The text had to be adjusted to reflect
this change as well.
Also, created a new variable entry for DEPLOY_DIR_IMAGE for
the glossary of the ref-manual.
(From yocto-docs rev: 50a68810f854b32fa5dba477eafa8fd1eebbd7a4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/closer-look.xml')
-rw-r--r-- | documentation/ref-manual/closer-look.xml | 34 |
1 files changed, 20 insertions, 14 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index f3f0db2..0947340 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -1079,13 +1079,16 @@ <para> Images are written out to the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> - inside the <filename>deploy/images</filename> folder as shown - in the figure. + inside the <filename>deploy/images/<machine>/</filename> + folder as shown in the figure. This folder contains any files expected to be loaded on the target device. The <link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link> - variable points to the <filename>deploy</filename> directory. + variable points to the <filename>deploy</filename> directory, + while the + <link linkend='var-DEPLOY_DIR_IMAGE'><filename>DEPLOY_DIR_IMAGE</filename></link> + variable points to the machine-specific directory. <itemizedlist> <listitem><para><filename><kernel-image></filename>: A kernel binary file. @@ -1094,8 +1097,9 @@ kernel image file. Depending on that variable, the file could begin with a variety of naming strings. - The <filename>deploy/images</filename> directory can - contain multiple image files.</para></listitem> + The <filename>deploy/images/<machine></filename> + directory can contain multiple image files for the + machine.</para></listitem> <listitem><para><filename><root-filesystem-image></filename>: Root filesystems for the target device (e.g. <filename>*.ext3</filename> or <filename>*.bz2</filename> @@ -1103,25 +1107,27 @@ The <link linkend='var-IMAGE_FSTYPES'><filename>IMAGE_FSTYPES</filename></link> variable setting determines the root filesystem image type. - The <filename>deploy/images</filename> directory can - contain multiple root filesystems.</para></listitem> + The <filename>deploy/images/<machine></filename> + directory can contain multiple root filesystems for the + machine.</para></listitem> <listitem><para><filename><kernel-modules></filename>: Tarballs that contain all the modules built for the kernel. Kernel module tarballs exist for legacy purposes and can be suppressed by setting the <link linkend='var-MODULE_TARBALL_DEPLOY'><filename>MODULE_TARBALL_DEPLOY</filename></link> variable to "0". - The <filename>deploy/images</filename> directory can - contain multiple kernel module tarballs. - </para></listitem> + The <filename>deploy/images/<machine></filename> + directory can contain multiple kernel module tarballs + for the machine.</para></listitem> <listitem><para><filename><bootloaders></filename>: Bootloaders supporting the image, if applicable to the target machine. - The <filename>deploy/images</filename> directory can - contain multiple bootloaders. - </para></listitem> + The <filename>deploy/images/<machine></filename> + directory can contain multiple bootloaders for the + machine.</para></listitem> <listitem><para><filename><symlinks></filename>: - The <filename>deploy/images</filename> folder contains + The <filename>deploy/images/<machine></filename> + folder contains a symbolic link that points to the most recently built file for each machine. These links might be useful for external scripts that |