summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/adt-manual')
-rw-r--r--documentation/adt-manual/adt-package.xml105
1 files changed, 65 insertions, 40 deletions
diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml
index 6139442ab5..fc2a1a0cba 100644
--- a/documentation/adt-manual/adt-package.xml
+++ b/documentation/adt-manual/adt-package.xml
@@ -2,55 +2,80 @@
2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> 2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
3 3
4<chapter id='adt-package'> 4<chapter id='adt-package'>
5<title>Optionally Customizing the Development Packages Installation</title>
6 <para>
7 Because the Yocto Project is suited for embedded Linux development it is
8 likely that you will need to customize your development packages installation.
9 For example, if you are developing a minimal image then you might not need
10 certain packages (e.g. graphics support packages).
11 Thus, you would like to be able to remove those packages from your sysroot.
12 </para>
5 13
6<title>Yocto Project Kernel Architecture and Use Manual</title> 14<section id='package-management-systems'>
15 <title>Package Management Systems</title>
16 <para>
17 The Yocto Project supports the generation of root filesystem files using
18 three different Package Management Systems (PMS):
19 <itemizedlist>
20 <listitem><para><emphasis>OPKG</emphasis> – A less well known PMS whose use
21 originated in the OpenEmbedded and OpenWrt embedded Linux projects.
22 This PMS works with files packaged in an <filename>.ipk</filename> format.
23 See <ulink url='http://en.wikipedia.org/wiki/Opkg'></ulink> for more
24 information about OPKG.</para></listitem>
25 <listitem><para><emphasis>RPM</emphasis> – A more widely known PMS intended for GNU/Linux
26 distributions.
27 This PMS works with files packaged in an <filename>.rms</filename> format.
28 The Yocto Project currently installs through this PMS by default.
29 See <ulink url='http://en.wikipedia.org/wiki/RPM_Package_Manager'></ulink>
30 for more information about RPM.</para></listitem>
31 <listitem><para><emphasis>Debian</emphasis> – The PMS for Debian-based systems
32 is built on many PMS tools.
33 The lower-level PMS tool dpkg forms the base of the Debian PMS.
34 For information on dpkg see
35 <ulink url='http://en.wikipedia.org/wiki/Dpkg'></ulink>.</para></listitem>
36 </itemizedlist>
37 </para>
38</section>
7 39
8<section id='package'> 40<section id='configuring-the-pms'>
9 <title>Introduction</title> 41 <title>Configuring the PMS</title>
42 <para>
43 Whichever PMS you are using you need to be sure that the
44 <filename>PACKAGE_CLASSES</filename> variable in the <filename>conf/local.conf</filename>
45 file is set to reflect that system.
46 The first value you choose for the variable specifies the package file format for the root
47 filesystem.
48 Additional values specify additional formats for convenience or testing.
49 See the configuration file for details.
50 </para>
10 <para> 51 <para>
11 The Yocto Project presents the kernel as a fully patched, history-clean git 52 As an example, consider a scenario where you are using OPKG and you want to add
12 repository. 53 the libglade package to sysroot.
13 The git tree represents the selected features, board support,
14 and configurations extensively tested by Yocto Project.
15 The Yocto Project kernel allows the end user to leverage community
16 best practices to seamlessly manage the development, build and debug cycles.
17 </para> 54 </para>
18 <para> 55 <para>
19 This manual describes the Yocto Project kernel by providing information 56 First, you should generate the ipk file for the libglade package and add it
20 on its history, organization, benefits, and use. 57 into a working opkg repository.
21 The manual consists of two sections: 58 Use these commands:
22 <itemizedlist> 59 <literallayout class='monospaced'>
23 <listitem><para>Concepts - Describes concepts behind the kernel. 60 $ bitbake libglade
24 You will understand how the kernel is organized and why it is organized in 61 $ bitbake package-index
25 the way it is. You will understand the benefits of the kernel's organization 62 </literallayout>
26 and the mechanisms used to work with the kernel and how to apply it in your
27 design process.</para></listitem>
28 <listitem><para>Using the Kernel - Describes best practices and "how-to" information
29 that lets you put the kernel to practical use. Some examples are "How to Build a
30 Project Specific Tree", "How to Examine Changes in a Branch", and "Saving Kernel
31 Modifications."</para></listitem>
32 </itemizedlist>
33 </para> 63 </para>
34 <para> 64 <para>
35 For more information on the kernel, see the following links: 65 Next, source the environment setup script.
36 <itemizedlist> 66 Follow that by setting up the installation destination to point to your
37 <listitem><para><ulink url='http://ldn.linuxfoundation.org/book/1-a-guide-kernel-development-process'></ulink></para></listitem> 67 sysroot as <filename>&lt;sysroot dir&gt;</filename>.
38 <listitem><para><ulink url='http://userweb.kernel.org/~akpm/stuff/tpp.txt'></ulink></para></listitem> 68 Finally, have an opkg configuration file <filename>&lt;conf file&gt;</filename>
39 <listitem><para><ulink url='http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/HOWTO;hb=HEAD'></ulink></para></listitem> 69 that corresponds to the opkg repository you have just created.
40 </itemizedlist> 70 The following command forms should now work:
41 <para> 71 <literallayout class='monospaced'>
42 You can find more information on Yocto Project by visiting the website at 72 $ opkg-cl –f &lt;conf file&gt; -o &lt;sysroot dir&gt; update
43 <ulink url='http://www.yoctoproject.org'></ulink>. 73 $ opkg-cl –f &lt;conf file&gt;> -o &lt;sysroot dir&gt; --force-overwrite install libglade
44 </para> 74 $ opkg-cl –f &lt;conf file&gt; -o &lt;sysroot dir&gt; --force-overwrite install libglade-dbg
75 $ opkg-cl –f &lt;conf file&gt; -o &lt;sysroot dir&gt; --force-overwrite install libglade-dev
76 </literallayout>
45 </para> 77 </para>
46</section> 78</section>
47
48
49
50
51
52
53
54</chapter> 79</chapter>
55<!-- 80<!--
56vim: expandtab tw=80 ts=4 81vim: expandtab tw=80 ts=4