diff options
Diffstat (limited to 'documentation/adt-manual/adt-package.xml')
-rw-r--r-- | documentation/adt-manual/adt-package.xml | 52 |
1 files changed, 29 insertions, 23 deletions
diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml index 449684d972..f7b236f8d5 100644 --- a/documentation/adt-manual/adt-package.xml +++ b/documentation/adt-manual/adt-package.xml | |||
@@ -3,6 +3,7 @@ | |||
3 | 3 | ||
4 | <chapter id='adt-package'> | 4 | <chapter id='adt-package'> |
5 | <title>Optionally Customizing the Development Packages Installation</title> | 5 | <title>Optionally Customizing the Development Packages Installation</title> |
6 | |||
6 | <para> | 7 | <para> |
7 | Because the Yocto Project is suited for embedded Linux development, it is | 8 | 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 | likely that you will need to customize your development packages installation. |
@@ -13,32 +14,34 @@ | |||
13 | 14 | ||
14 | <section id='package-management-systems'> | 15 | <section id='package-management-systems'> |
15 | <title>Package Management Systems</title> | 16 | <title>Package Management Systems</title> |
17 | |||
16 | <para> | 18 | <para> |
17 | The Yocto Project supports the generation of sysroot files using | 19 | The Yocto Project supports the generation of sysroot files using |
18 | three different Package Management Systems (PMS): | 20 | three different Package Management Systems (PMS): |
19 | <itemizedlist> | 21 | <itemizedlist> |
20 | <listitem><para><emphasis>OPKG</emphasis> – A less well known PMS whose use | 22 | <listitem><para><emphasis>OPKG:</emphasis> A less well known PMS whose use |
21 | originated in the OpenEmbedded and OpenWrt embedded Linux projects. | 23 | originated in the OpenEmbedded and OpenWrt embedded Linux projects. |
22 | This PMS works with files packaged in an <filename>.ipk</filename> format. | 24 | 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 | 25 | See <ulink url='http://en.wikipedia.org/wiki/Opkg'></ulink> for more |
24 | information about OPKG.</para></listitem> | 26 | information about OPKG.</para></listitem> |
25 | <listitem><para><emphasis>RPM</emphasis> – A more widely known PMS intended for GNU/Linux | 27 | <listitem><para><emphasis>RPM:</emphasis> A more widely known PMS intended for GNU/Linux |
26 | distributions. | 28 | distributions. |
27 | This PMS works with files packaged in an <filename>.rms</filename> format. | 29 | This PMS works with files packaged in an <filename>.rms</filename> format. |
28 | The Yocto Project currently installs through this PMS by default. | 30 | The Yocto Project currently installs through this PMS by default. |
29 | See <ulink url='http://en.wikipedia.org/wiki/RPM_Package_Manager'></ulink> | 31 | See <ulink url='http://en.wikipedia.org/wiki/RPM_Package_Manager'></ulink> |
30 | for more information about RPM.</para></listitem> | 32 | for more information about RPM.</para></listitem> |
31 | <listitem><para><emphasis>Debian</emphasis> – The PMS for Debian-based systems | 33 | <listitem><para><emphasis>Debian:</emphasis> The PMS for Debian-based systems |
32 | is built on many PMS tools. | 34 | is built on many PMS tools. |
33 | The lower-level PMS tool <filename>dpkg</filename> forms the base of the Debian PMS. | 35 | The lower-level PMS tool <filename>dpkg</filename> forms the base of the Debian PMS. |
34 | For information on dpkg see | 36 | For information on dpkg see |
35 | <ulink url='http://en.wikipedia.org/wiki/Dpkg'></ulink>.</para></listitem> | 37 | <ulink url='http://en.wikipedia.org/wiki/Dpkg'></ulink>.</para></listitem> |
36 | </itemizedlist> | 38 | </itemizedlist> |
37 | </para> | 39 | </para> |
38 | </section> | 40 | </section> |
39 | 41 | ||
40 | <section id='configuring-the-pms'> | 42 | <section id='configuring-the-pms'> |
41 | <title>Configuring the PMS</title> | 43 | <title>Configuring the PMS</title> |
44 | |||
42 | <para> | 45 | <para> |
43 | Whichever PMS you are using, you need to be sure that the | 46 | 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> | 47 | <filename>PACKAGE_CLASSES</filename> variable in the <filename>conf/local.conf</filename> |
@@ -48,10 +51,12 @@ | |||
48 | Additional values specify additional formats for convenience or testing. | 51 | Additional values specify additional formats for convenience or testing. |
49 | See the configuration file for details. | 52 | See the configuration file for details. |
50 | </para> | 53 | </para> |
54 | |||
51 | <para> | 55 | <para> |
52 | As an example, consider a scenario where you are using OPKG and you want to add | 56 | As an example, consider a scenario where you are using OPKG and you want to add |
53 | the <filename>libglade</filename> package to the target sysroot. | 57 | the <filename>libglade</filename> package to the target sysroot. |
54 | </para> | 58 | </para> |
59 | |||
55 | <para> | 60 | <para> |
56 | First, you should generate the <filename>ipk</filename> file for the | 61 | First, you should generate the <filename>ipk</filename> file for the |
57 | <filename>libglade</filename> package and add it | 62 | <filename>libglade</filename> package and add it |
@@ -62,20 +67,21 @@ | |||
62 | $ bitbake package-index | 67 | $ bitbake package-index |
63 | </literallayout> | 68 | </literallayout> |
64 | </para> | 69 | </para> |
70 | |||
65 | <para> | 71 | <para> |
66 | Next, source the environment setup script found in the Yocto Project files. | 72 | Next, source the environment setup script found in the Yocto Project files. |
67 | Follow that by setting up the installation destination to point to your | 73 | Follow that by setting up the installation destination to point to your |
68 | sysroot as <filename><sysroot_dir></filename>. | 74 | sysroot as <filename><sysroot_dir></filename>. |
69 | Finally, have an <filename>opkg</filename> configuration file <filename><conf_file></filename> | 75 | Finally, have an OPKG configuration file <filename><conf_file></filename> |
70 | that corresponds to the <filename>opkg</filename> repository you have just created. | 76 | that corresponds to the <filename>opkg</filename> repository you have just created. |
71 | The following command forms should now work: | 77 | The following command forms should now work: |
72 | <literallayout class='monospaced'> | 78 | <literallayout class='monospaced'> |
73 | $ opkg-cl –f <conf_file> -o <sysroot-dir> update | 79 | $ opkg-cl –f <conf_file> -o <sysroot_dir> update |
74 | $ opkg-cl –f <cconf_file> -o <sysroot-dir> \ | 80 | $ opkg-cl –f <cconf_file> -o <sysroot_dir> \ |
75 | --force-overwrite install libglade | 81 | --force-overwrite install libglade |
76 | $ opkg-cl –f <cconf_file> -o <sysroot-dir> \ | 82 | $ opkg-cl –f <cconf_file> -o <sysroot_dir> \ |
77 | --force-overwrite install libglade-dbg | 83 | --force-overwrite install libglade-dbg |
78 | $ opkg-cl –f <conf_file> -o <sysroot-dir> \ | 84 | $ opkg-cl –f <conf_file> -o <sysroot_dir> \ |
79 | --force-overwrite install libglade-dev | 85 | --force-overwrite install libglade-dev |
80 | </literallayout> | 86 | </literallayout> |
81 | </para> | 87 | </para> |