diff options
Diffstat (limited to 'documentation/getting-started/eclipse/html/getting-started/package-feeds-dev-environment.html')
-rw-r--r-- | documentation/getting-started/eclipse/html/getting-started/package-feeds-dev-environment.html | 98 |
1 files changed, 98 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/package-feeds-dev-environment.html b/documentation/getting-started/eclipse/html/getting-started/package-feeds-dev-environment.html new file mode 100644 index 0000000000..ad3d67f660 --- /dev/null +++ b/documentation/getting-started/eclipse/html/getting-started/package-feeds-dev-environment.html | |||
@@ -0,0 +1,98 @@ | |||
1 | <html> | ||
2 | <head> | ||
3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
4 | <title>2.8.4. Package Feeds</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="source-mirrors.html" title="2.8.3.4. Source Mirror(s)"> | ||
10 | <link rel="next" href="bitbake-dev-environment.html" title="2.8.5. BitBake"> | ||
11 | </head> | ||
12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.8.4. Package Feeds"> | ||
13 | <div class="titlepage"><div><div><h3 class="title"> | ||
14 | <a name="package-feeds-dev-environment"></a>2.8.4. Package Feeds</h3></div></div></div> | ||
15 | <p> | ||
16 | When the OpenEmbedded build system generates an image or an SDK, | ||
17 | it gets the packages from a package feed area located in the | ||
18 | <a class="link" href="../ref-manual/build-directory.html" target="_self">Build Directory</a>. | ||
19 | The | ||
20 | <a class="link" href="development-concepts.html#general-yocto-environment-figure">general Yocto Project Development Environment figure</a> | ||
21 | shows this package feeds area in the upper-right corner. | ||
22 | </p> | ||
23 | <p> | ||
24 | This section looks a little closer into the package feeds area used | ||
25 | by the build system. | ||
26 | Here is a more detailed look at the area: | ||
27 | </p> | ||
28 | <table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="630"><tr style="height: 540px"><td align="center"><img src="figures/package-feeds.png" align="middle" width="630"></td></tr></table> | ||
29 | <p> | ||
30 | </p> | ||
31 | <p> | ||
32 | Package feeds are an intermediary step in the build process. | ||
33 | The OpenEmbedded build system provides classes to generate | ||
34 | different package types, and you specify which classes to enable | ||
35 | through the | ||
36 | <a class="link" href="../ref-manual/var-PACKAGE_CLASSES.html" target="_self"><code class="filename">PACKAGE_CLASSES</code></a> | ||
37 | variable. | ||
38 | Before placing the packages into package feeds, | ||
39 | the build process validates them with generated output quality | ||
40 | assurance checks through the | ||
41 | <a class="link" href="../ref-manual/ref-classes-insane.html" target="_self"><code class="filename">insane</code></a> | ||
42 | class. | ||
43 | </p> | ||
44 | <p> | ||
45 | The package feed area resides in the Build Directory. | ||
46 | The directory the build system uses to temporarily store packages | ||
47 | is determined by a combination of variables and the particular | ||
48 | package manager in use. | ||
49 | See the "Package Feeds" box in the illustration and note the | ||
50 | information to the right of that area. | ||
51 | In particular, the following defines where package files are | ||
52 | kept: | ||
53 | </p> | ||
54 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
55 | <li class="listitem"><p><a class="link" href="../ref-manual/var-DEPLOY_DIR.html" target="_self"><code class="filename">DEPLOY_DIR</code></a>: | ||
56 | Defined as <code class="filename">tmp/deploy</code> in the Build | ||
57 | Directory. | ||
58 | </p></li> | ||
59 | <li class="listitem"><p><code class="filename">DEPLOY_DIR_*</code>: | ||
60 | Depending on the package manager used, the package type | ||
61 | sub-folder. | ||
62 | Given RPM, IPK, or DEB packaging and tarball creation, the | ||
63 | <a class="link" href="../ref-manual/var-DEPLOY_DIR_RPM.html" target="_self"><code class="filename">DEPLOY_DIR_RPM</code></a>, | ||
64 | <a class="link" href="../ref-manual/var-DEPLOY_DIR_IPK.html" target="_self"><code class="filename">DEPLOY_DIR_IPK</code></a>, | ||
65 | <a class="link" href="../ref-manual/var-DEPLOY_DIR_DEB.html" target="_self"><code class="filename">DEPLOY_DIR_DEB</code></a>, | ||
66 | or | ||
67 | <a class="link" href="../ref-manual/var-DEPLOY_DIR_TAR.html" target="_self"><code class="filename">DEPLOY_DIR_TAR</code></a>, | ||
68 | variables are used, respectively. | ||
69 | </p></li> | ||
70 | <li class="listitem"><p><a class="link" href="../ref-manual/var-PACKAGE_ARCH.html" target="_self"><code class="filename">PACKAGE_ARCH</code></a>: | ||
71 | Defines architecture-specific sub-folders. | ||
72 | For example, packages could exist for the i586 or qemux86 | ||
73 | architectures. | ||
74 | </p></li> | ||
75 | </ul></div> | ||
76 | <p> | ||
77 | </p> | ||
78 | <p> | ||
79 | BitBake uses the <code class="filename">do_package_write_*</code> tasks to | ||
80 | generate packages and place them into the package holding area (e.g. | ||
81 | <code class="filename">do_package_write_ipk</code> for IPK packages). | ||
82 | See the | ||
83 | "<a class="link" href="../ref-manual/ref-tasks-package_write_deb.html" target="_self"><code class="filename">do_package_write_deb</code></a>", | ||
84 | "<a class="link" href="../ref-manual/ref-tasks-package_write_ipk.html" target="_self"><code class="filename">do_package_write_ipk</code></a>", | ||
85 | "<a class="link" href="../ref-manual/ref-tasks-package_write_rpm.html" target="_self"><code class="filename">do_package_write_rpm</code></a>", | ||
86 | and | ||
87 | "<a class="link" href="../ref-manual/ref-tasks-package_write_tar.html" target="_self"><code class="filename">do_package_write_tar</code></a>" | ||
88 | sections for additional information. | ||
89 | As an example, consider a scenario where an IPK packaging manager | ||
90 | is being used and package architecture support for both i586 | ||
91 | and qemux86 exist. | ||
92 | Packages for the i586 architecture are placed in | ||
93 | <code class="filename">build/tmp/deploy/ipk/i586</code>, while packages for | ||
94 | the qemux86 architecture are placed in | ||
95 | <code class="filename">build/tmp/deploy/ipk/qemux86</code>. | ||
96 | </p> | ||
97 | </div></body> | ||
98 | </html> | ||