summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
Diffstat (limited to 'documentation')
-rw-r--r--documentation/mega-manual/figures/analysis-for-package-splitting.pngbin0 -> 58199 bytes
-rw-r--r--documentation/ref-manual/figures/analysis-for-package-splitting.pngbin0 -> 58199 bytes
-rw-r--r--documentation/ref-manual/technical-details.xml54
3 files changed, 54 insertions, 0 deletions
diff --git a/documentation/mega-manual/figures/analysis-for-package-splitting.png b/documentation/mega-manual/figures/analysis-for-package-splitting.png
new file mode 100644
index 0000000000..5edf62c706
--- /dev/null
+++ b/documentation/mega-manual/figures/analysis-for-package-splitting.png
Binary files differ
diff --git a/documentation/ref-manual/figures/analysis-for-package-splitting.png b/documentation/ref-manual/figures/analysis-for-package-splitting.png
new file mode 100644
index 0000000000..5edf62c706
--- /dev/null
+++ b/documentation/ref-manual/figures/analysis-for-package-splitting.png
Binary files differ
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 260766191a..1b67ca7424 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -1125,6 +1125,60 @@
1125 </itemizedlist> 1125 </itemizedlist>
1126 </para> 1126 </para>
1127 </section> 1127 </section>
1128
1129 <section id='package-splitting-dev-environment'>
1130 <title>Package Splitting</title>
1131
1132 <para>
1133 After source code configured and compiled, BitBake analyzes
1134 the results and splits the output into package:
1135 <imagedata fileref="figures/analysis-for-package-splitting.png" align="center" width="7in" depth="7in" />
1136 </para>
1137
1138 <para>
1139 The <filename>do_package</filename> and
1140 <filename>do_packagedata</filename> tasks combine to analyze
1141 the data found in the
1142 <link linkend='var-D'><filename>D</filename></link> directory
1143 and split it into subsets based on available packages and
1144 files.
1145 The analyzing process involves splitting out debugging symbols,
1146 looking at shared library dependencies between packages, and
1147 looking at package relationships.
1148 The <filename>do_packagedata</filename> task puts package
1149 metadata based on the analysis such that BitBake can generate
1150 the final packages.
1151 Intermediate results of the package analysis and splitting
1152 end up in the
1153 <link linkend='var-PKGDEST'><filename>PKGDEST</filename></link>
1154 directory with the
1155 <link linkend='var-FILES'><filename>FILES</filename></link>
1156 variable defining the files that go into the packages.
1157 If you want some details on how this is accomplished, you can
1158 look at
1159 <link linkend='ref-classes-package'><filename>package.bbclass</filename></link>.
1160 </para>
1161
1162 <para>
1163 Depending on the type of packages being created (RPM, DEB, or
1164 IPK), the <filename>do_packagewrite_*</filename> task
1165 creates the actual packages and places them in the
1166 Package Feed area, which is
1167 <filename>${TMPDIR}/deploy</filename>.
1168 You can see the
1169 "<link linkend='package-feeds-dev-environment'>Package Feeds</link>"
1170 section for more detail on that part of the build process.
1171 <note>
1172 Support for creating feeds directly from the
1173 <filename>deploy/*</filename> directories does not exist.
1174 Creating such feeds usually requires some kind of feed
1175 maintenance mechanism that would upload the new packages
1176 into an official package feed (e.g. angstrom).
1177 Providing such a piece for the user is not feasible since
1178 it is very distribution-specific.
1179 </note>
1180 </para>
1181 </section>
1128 </section> 1182 </section>
1129</section> 1183</section>
1130 1184