summaryrefslogtreecommitdiffstats
path: root/documentation/getting-started/eclipse/html/getting-started/package-splitting-dev-environment.html
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/getting-started/eclipse/html/getting-started/package-splitting-dev-environment.html')
-rw-r--r--documentation/getting-started/eclipse/html/getting-started/package-splitting-dev-environment.html94
1 files changed, 94 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/package-splitting-dev-environment.html b/documentation/getting-started/eclipse/html/getting-started/package-splitting-dev-environment.html
new file mode 100644
index 0000000000..882d66c31c
--- /dev/null
+++ b/documentation/getting-started/eclipse/html/getting-started/package-splitting-dev-environment.html
@@ -0,0 +1,94 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.8.5.4. Package Splitting</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="bitbake-dev-environment.html" title="2.8.5. BitBake">
9<link rel="prev" href="configuration-and-compilation-dev-environment.html" title="2.8.5.3. Configuration and Compilation">
10<link rel="next" href="image-generation-dev-environment.html" title="2.8.5.5. Image Generation">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.8.5.4. Package Splitting">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="package-splitting-dev-environment"></a>2.8.5.4. Package Splitting</h4></div></div></div>
15<p>
16 After source code is configured and compiled, the
17 OpenEmbedded build system analyzes
18 the results and splits the output into packages:
19 </p>
20<table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="630"><tr style="height: 630px"><td align="center"><img src="figures/analysis-for-package-splitting.png" align="middle" width="630"></td></tr></table>
21<p>
22 </p>
23<p>
24 The
25 <a class="link" href="../ref-manual/ref-tasks-package.html" target="_self"><code class="filename">do_package</code></a>
26 and
27 <a class="link" href="../ref-manual/ref-tasks-packagedata.html" target="_self"><code class="filename">do_packagedata</code></a>
28 tasks combine to analyze
29 the files found in the
30 <a class="link" href="../ref-manual/var-D.html" target="_self"><code class="filename">D</code></a> directory
31 and split them into subsets based on available packages and
32 files.
33 The analyzing process involves the following as well as other
34 items: splitting out debugging symbols,
35 looking at shared library dependencies between packages,
36 and looking at package relationships.
37 The <code class="filename">do_packagedata</code> task creates package
38 metadata based on the analysis such that the
39 OpenEmbedded build system can generate the final packages.
40 Working, staged, and intermediate results of the analysis
41 and package splitting process use these areas:
42 </p>
43<div class="itemizedlist"><ul class="itemizedlist" type="disc">
44<li class="listitem"><p><a class="link" href="../ref-manual/var-PKGD.html" target="_self"><code class="filename">PKGD</code></a> -
45 The destination directory for packages before they are
46 split.
47 </p></li>
48<li class="listitem"><p><a class="link" href="../ref-manual/var-PKGDATA_DIR.html" target="_self"><code class="filename">PKGDATA_DIR</code></a> -
49 A shared, global-state directory that holds data
50 generated during the packaging process.
51 </p></li>
52<li class="listitem"><p><a class="link" href="../ref-manual/var-PKGDESTWORK.html" target="_self"><code class="filename">PKGDESTWORK</code></a> -
53 A temporary work area used by the
54 <code class="filename">do_package</code> task.
55 </p></li>
56<li class="listitem"><p><a class="link" href="../ref-manual/var-PKGDEST.html" target="_self"><code class="filename">PKGDEST</code></a> -
57 The parent directory for packages after they have
58 been split.
59 </p></li>
60</ul></div>
61<p>
62 The <a class="link" href="../ref-manual/var-FILES.html" target="_self"><code class="filename">FILES</code></a>
63 variable defines the files that go into each package in
64 <a class="link" href="../ref-manual/var-PACKAGES.html" target="_self"><code class="filename">PACKAGES</code></a>.
65 If you want details on how this is accomplished, you can
66 look at the
67 <a class="link" href="../ref-manual/ref-classes-package.html" target="_self"><code class="filename">package</code></a>
68 class.
69 </p>
70<p>
71 Depending on the type of packages being created (RPM, DEB, or
72 IPK), the <code class="filename">do_package_write_*</code> task
73 creates the actual packages and places them in the
74 Package Feed area, which is
75 <code class="filename">${TMPDIR}/deploy</code>.
76 You can see the
77 "<a class="link" href="package-feeds-dev-environment.html" title="2.8.4. Package Feeds">Package Feeds</a>"
78 section for more detail on that part of the build process.
79 </p>
80<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
81<h3 class="title">Note</h3>
82 Support for creating feeds directly from the
83 <code class="filename">deploy/*</code> directories does not exist.
84 Creating such feeds usually requires some kind of feed
85 maintenance mechanism that would upload the new packages
86 into an official package feed (e.g. the
87 Ångström distribution).
88 This functionality is highly distribution-specific
89 and thus is not provided out of the box.
90 </div>
91<p>
92 </p>
93</div></body>
94</html>