summaryrefslogtreecommitdiffstats
path: root/documentation/getting-started/eclipse/html/getting-started/images-dev-environment.html
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/getting-started/eclipse/html/getting-started/images-dev-environment.html')
-rw-r--r--documentation/getting-started/eclipse/html/getting-started/images-dev-environment.html99
1 files changed, 99 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/images-dev-environment.html b/documentation/getting-started/eclipse/html/getting-started/images-dev-environment.html
new file mode 100644
index 0000000000..2561f1f4a6
--- /dev/null
+++ b/documentation/getting-started/eclipse/html/getting-started/images-dev-environment.html
@@ -0,0 +1,99 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.8.6. Images</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="Getting Started With Yocto Project">
8<link rel="up" href="development-concepts.html" title="2.8. Development Concepts">
9<link rel="prev" href="setscene-tasks-and-shared-state.html" title="2.8.5.8. Setscene Tasks and Shared State">
10<link rel="next" href="sdk-dev-environment.html" title="2.8.7. Application Development SDK">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.8.6. Images">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="images-dev-environment"></a>2.8.6. Images</h3></div></div></div>
15<p>
16 The images produced by the OpenEmbedded build system
17 are compressed forms of the
18 root filesystem that are ready to boot on a target device.
19 You can see from the
20 <a class="link" href="development-concepts.html#general-yocto-environment-figure">general Yocto Project Development Environment figure</a>
21 that BitBake output, in part, consists of images.
22 This section is going to look more closely at this output:
23 </p>
24<table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="495"><tr style="height: 495px"><td align="center"><img src="figures/images.png" align="middle" width="495"></td></tr></table>
25<p>
26 </p>
27<p>
28 For a list of example images that the Yocto Project provides,
29 see the
30 "<a class="link" href="../ref-manual/ref-images.html" target="_self">Images</a>"
31 chapter in the Yocto Project Reference Manual.
32 </p>
33<p>
34 Images are written out to the
35 <a class="link" href="../ref-manual/build-directory.html" target="_self">Build Directory</a>
36 inside the
37 <code class="filename">tmp/deploy/images/<em class="replaceable"><code>machine</code></em>/</code>
38 folder as shown in the figure.
39 This folder contains any files expected to be loaded on the
40 target device.
41 The
42 <a class="link" href="../ref-manual/var-DEPLOY_DIR.html" target="_self"><code class="filename">DEPLOY_DIR</code></a>
43 variable points to the <code class="filename">deploy</code> directory,
44 while the
45 <a class="link" href="../ref-manual/var-DEPLOY_DIR_IMAGE.html" target="_self"><code class="filename">DEPLOY_DIR_IMAGE</code></a>
46 variable points to the appropriate directory containing images for
47 the current configuration.
48 </p>
49<div class="itemizedlist"><ul class="itemizedlist" type="disc">
50<li class="listitem"><p><code class="filename"><em class="replaceable"><code>kernel-image</code></em></code>:
51 A kernel binary file.
52 The
53 <a class="link" href="../ref-manual/var-KERNEL_IMAGETYPE.html" target="_self"><code class="filename">KERNEL_IMAGETYPE</code></a>
54 variable setting determines the naming scheme for the
55 kernel image file.
56 Depending on that variable, the file could begin with
57 a variety of naming strings.
58 The <code class="filename">deploy/images/<em class="replaceable"><code>machine</code></em></code>
59 directory can contain multiple image files for the
60 machine.</p></li>
61<li class="listitem"><p><code class="filename"><em class="replaceable"><code>root-filesystem-image</code></em></code>:
62 Root filesystems for the target device (e.g.
63 <code class="filename">*.ext3</code> or <code class="filename">*.bz2</code>
64 files).
65 The
66 <a class="link" href="../ref-manual/var-IMAGE_FSTYPES.html" target="_self"><code class="filename">IMAGE_FSTYPES</code></a>
67 variable setting determines the root filesystem image
68 type.
69 The <code class="filename">deploy/images/<em class="replaceable"><code>machine</code></em></code>
70 directory can contain multiple root filesystems for the
71 machine.</p></li>
72<li class="listitem"><p><code class="filename"><em class="replaceable"><code>kernel-modules</code></em></code>:
73 Tarballs that contain all the modules built for the kernel.
74 Kernel module tarballs exist for legacy purposes and
75 can be suppressed by setting the
76 <a class="link" href="../ref-manual/var-MODULE_TARBALL_DEPLOY.html" target="_self"><code class="filename">MODULE_TARBALL_DEPLOY</code></a>
77 variable to "0".
78 The <code class="filename">deploy/images/<em class="replaceable"><code>machine</code></em></code>
79 directory can contain multiple kernel module tarballs
80 for the machine.</p></li>
81<li class="listitem"><p><code class="filename"><em class="replaceable"><code>bootloaders</code></em></code>:
82 Bootloaders supporting the image, if applicable to the
83 target machine.
84 The <code class="filename">deploy/images/<em class="replaceable"><code>machine</code></em></code>
85 directory can contain multiple bootloaders for the
86 machine.</p></li>
87<li class="listitem"><p><code class="filename"><em class="replaceable"><code>symlinks</code></em></code>:
88 The <code class="filename">deploy/images/<em class="replaceable"><code>machine</code></em></code>
89 folder contains
90 a symbolic link that points to the most recently built file
91 for each machine.
92 These links might be useful for external scripts that
93 need to obtain the latest version of each file.
94 </p></li>
95</ul></div>
96<p>
97 </p>
98</div></body>
99</html>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-04-30 21:21:35 +0000