diff options
Diffstat (limited to 'documentation/ref-manual/closer-look.xml')
| -rw-r--r-- | documentation/ref-manual/closer-look.xml | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index f0ed967228..c0c0d619a4 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -255,7 +255,7 @@ <para> When you launch your build with the - <filename>bitbake <target></filename> command, BitBake + <filename>bitbake <replaceable>target</replaceable></filename> command, BitBake sorts out the configurations to ultimately define your build environment. </para> @@ -351,7 +351,7 @@ Best practices dictate that you isolate these types of configurations into their own layer. Settings you provide in - <filename>conf/distro/<distro>.conf</filename> override + <filename>conf/distro/<replaceable>distro</replaceable>.conf</filename> override similar settings that BitBake finds in your <filename>conf/local.conf</filename> file in the Build @@ -375,7 +375,7 @@ This area holds configuration files for the layer (<filename>conf/layer.conf</filename>), the distribution - (<filename>conf/distro/<distro>.conf</filename>), + (<filename>conf/distro/<replaceable>distro</replaceable>.conf</filename>), and any distribution-wide include files. </para></listitem> <listitem><para><emphasis>recipes-*:</emphasis> @@ -408,7 +408,7 @@ <para> The BSP Layer's configuration directory contains configuration files for the machine - (<filename>conf/machine/<machine>.conf</filename>) and, + (<filename>conf/machine/<replaceable>machine</replaceable>.conf</filename>) and, of course, the layer (<filename>conf/layer.conf</filename>). </para> @@ -1145,7 +1145,7 @@ <para> Images are written out to the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> - inside the <filename>tmp/deploy/images/<machine>/</filename> + inside the <filename>tmp/deploy/images/<replaceable>machine</replaceable>/</filename> folder as shown in the figure. This folder contains any files expected to be loaded on the target device. @@ -1157,43 +1157,43 @@ variable points to the appropriate directory containing images for the current configuration. <itemizedlist> - <listitem><para><filename><kernel-image></filename>: + <listitem><para><filename><replaceable>kernel-image</replaceable></filename>: A kernel binary file. The <link linkend='var-KERNEL_IMAGETYPE'><filename>KERNEL_IMAGETYPE</filename></link> variable setting determines the naming scheme for the kernel image file. Depending on that variable, the file could begin with a variety of naming strings. - The <filename>deploy/images/<machine></filename> + The <filename>deploy/images/<replaceable>machine</replaceable></filename> directory can contain multiple image files for the machine.</para></listitem> - <listitem><para><filename><root-filesystem-image></filename>: + <listitem><para><filename><replaceable>root-filesystem-image</replaceable></filename>: Root filesystems for the target device (e.g. <filename>*.ext3</filename> or <filename>*.bz2</filename> files). The <link linkend='var-IMAGE_FSTYPES'><filename>IMAGE_FSTYPES</filename></link> variable setting determines the root filesystem image type. - The <filename>deploy/images/<machine></filename> + The <filename>deploy/images/<replaceable>machine</replaceable></filename> directory can contain multiple root filesystems for the machine.</para></listitem> - <listitem><para><filename><kernel-modules></filename>: + <listitem><para><filename><replaceable>kernel-modules</replaceable></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/<machine></filename> + The <filename>deploy/images/<replaceable>machine</replaceable></filename> directory can contain multiple kernel module tarballs for the machine.</para></listitem> - <listitem><para><filename><bootloaders></filename>: + <listitem><para><filename><replaceable>bootloaders</replaceable></filename>: Bootloaders supporting the image, if applicable to the target machine. - The <filename>deploy/images/<machine></filename> + The <filename>deploy/images/<replaceable>machine</replaceable></filename> directory can contain multiple bootloaders for the machine.</para></listitem> - <listitem><para><filename><symlinks></filename>: - The <filename>deploy/images/<machine></filename> + <listitem><para><filename><replaceable>symlinks</replaceable></filename>: + The <filename>deploy/images/<replaceable>machine</replaceable></filename> folder contains a symbolic link that points to the most recently built file for each machine. @@ -1280,7 +1280,7 @@ part of the SDK (i.e. the part that runs on the <filename>SDKMACHINE</filename>). When you use - <filename>bitbake -c populate_sdk <imagename></filename> + <filename>bitbake -c populate_sdk <replaceable>imagename</replaceable></filename> to create the SDK, a set of default packages apply. This variable allows you to add more packages. |