summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-package.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-12-07 17:19:36 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-12-11 16:15:24 +0000
commit3bcdba62b186c554033357bb50de0b20d115a54d (patch)
treeabc1731f63ac3faeec778c39e45344d61c3d7949 /documentation/adt-manual/adt-package.xml
parent205c7961f31fced8f42a8fc483618ed3d54dc109 (diff)
downloadpoky-3bcdba62b186c554033357bb50de0b20d115a54d.tar.gz
documentation: adt-manual - Removed all trailing whitespace.
(From yocto-docs rev: c1c271c0404dff9ed49597a4582a56def8237dd7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual/adt-package.xml')
-rw-r--r--documentation/adt-manual/adt-package.xml54
1 files changed, 27 insertions, 27 deletions
diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml
index da8d10fa4b..9e68c3131e 100644
--- a/documentation/adt-manual/adt-package.xml
+++ b/documentation/adt-manual/adt-package.xml
@@ -6,10 +6,10 @@
6<title>Optionally Customizing the Development Packages Installation</title> 6<title>Optionally Customizing the Development Packages Installation</title>
7 7
8 <para> 8 <para>
9 Because the Yocto Project is suited for embedded Linux development, it is 9 Because the Yocto Project is suited for embedded Linux development, it is
10 likely that you will need to customize your development packages installation. 10 likely that you will need to customize your development packages installation.
11 For example, if you are developing a minimal image, then you might not need 11 For example, if you are developing a minimal image, then you might not need
12 certain packages (e.g. graphics support packages). 12 certain packages (e.g. graphics support packages).
13 Thus, you would like to be able to remove those packages from your target sysroot. 13 Thus, you would like to be able to remove those packages from your target sysroot.
14 </para> 14 </para>
15 15
@@ -17,24 +17,24 @@
17 <title>Package Management Systems</title> 17 <title>Package Management Systems</title>
18 18
19 <para> 19 <para>
20 The OpenEmbedded build system supports the generation of sysroot files using 20 The OpenEmbedded build system supports the generation of sysroot files using
21 three different Package Management Systems (PMS): 21 three different Package Management Systems (PMS):
22 <itemizedlist> 22 <itemizedlist>
23 <listitem><para><emphasis>OPKG:</emphasis> A less well known PMS whose use 23 <listitem><para><emphasis>OPKG:</emphasis> A less well known PMS whose use
24 originated in the OpenEmbedded and OpenWrt embedded Linux projects. 24 originated in the OpenEmbedded and OpenWrt embedded Linux projects.
25 This PMS works with files packaged in an <filename>.ipk</filename> format. 25 This PMS works with files packaged in an <filename>.ipk</filename> format.
26 See <ulink url='http://en.wikipedia.org/wiki/Opkg'></ulink> for more 26 See <ulink url='http://en.wikipedia.org/wiki/Opkg'></ulink> for more
27 information about OPKG.</para></listitem> 27 information about OPKG.</para></listitem>
28 <listitem><para><emphasis>RPM:</emphasis> A more widely known PMS intended for GNU/Linux 28 <listitem><para><emphasis>RPM:</emphasis> A more widely known PMS intended for GNU/Linux
29 distributions. 29 distributions.
30 This PMS works with files packaged in an <filename>.rms</filename> format. 30 This PMS works with files packaged in an <filename>.rms</filename> format.
31 The build system currently installs through this PMS by default. 31 The build system currently installs through this PMS by default.
32 See <ulink url='http://en.wikipedia.org/wiki/RPM_Package_Manager'></ulink> 32 See <ulink url='http://en.wikipedia.org/wiki/RPM_Package_Manager'></ulink>
33 for more information about RPM.</para></listitem> 33 for more information about RPM.</para></listitem>
34 <listitem><para><emphasis>Debian:</emphasis> The PMS for Debian-based systems 34 <listitem><para><emphasis>Debian:</emphasis> The PMS for Debian-based systems
35 is built on many PMS tools. 35 is built on many PMS tools.
36 The lower-level PMS tool <filename>dpkg</filename> forms the base of the Debian PMS. 36 The lower-level PMS tool <filename>dpkg</filename> forms the base of the Debian PMS.
37 For information on dpkg see 37 For information on dpkg see
38 <ulink url='http://en.wikipedia.org/wiki/Dpkg'></ulink>.</para></listitem> 38 <ulink url='http://en.wikipedia.org/wiki/Dpkg'></ulink>.</para></listitem>
39 </itemizedlist> 39 </itemizedlist>
40 </para> 40 </para>
@@ -44,13 +44,13 @@
44 <title>Configuring the PMS</title> 44 <title>Configuring the PMS</title>
45 45
46 <para> 46 <para>
47 Whichever PMS you are using, you need to be sure that the 47 Whichever PMS you are using, you need to be sure that the
48 <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink> 48 <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink>
49 variable in the <filename>conf/local.conf</filename> 49 variable in the <filename>conf/local.conf</filename>
50 file is set to reflect that system. 50 file is set to reflect that system.
51 The first value you choose for the variable specifies the package file format for the root 51 The first value you choose for the variable specifies the package file format for the root
52 filesystem at sysroot. 52 filesystem at sysroot.
53 Additional values specify additional formats for convenience or testing. 53 Additional values specify additional formats for convenience or testing.
54 See the configuration file for details. 54 See the configuration file for details.
55 </para> 55 </para>
56 56
@@ -61,14 +61,14 @@
61 </note> 61 </note>
62 62
63 <para> 63 <para>
64 As an example, consider a scenario where you are using OPKG and you want to add 64 As an example, consider a scenario where you are using OPKG and you want to add
65 the <filename>libglade</filename> package to the target sysroot. 65 the <filename>libglade</filename> package to the target sysroot.
66 </para> 66 </para>
67 67
68 <para> 68 <para>
69 First, you should generate the <filename>ipk</filename> file for the 69 First, you should generate the <filename>ipk</filename> file for the
70 <filename>libglade</filename> package and add it 70 <filename>libglade</filename> package and add it
71 into a working <filename>opkg</filename> repository. 71 into a working <filename>opkg</filename> repository.
72 Use these commands: 72 Use these commands:
73 <literallayout class='monospaced'> 73 <literallayout class='monospaced'>
74 $ bitbake libglade 74 $ bitbake libglade
@@ -77,12 +77,12 @@
77 </para> 77 </para>
78 78
79 <para> 79 <para>
80 Next, source the environment setup script found in the 80 Next, source the environment setup script found in the
81 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 81 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
82 Follow that by setting up the installation destination to point to your 82 Follow that by setting up the installation destination to point to your
83 sysroot as <filename>&lt;sysroot_dir&gt;</filename>. 83 sysroot as <filename>&lt;sysroot_dir&gt;</filename>.
84 Finally, have an OPKG configuration file <filename>&lt;conf_file&gt;</filename> 84 Finally, have an OPKG configuration file <filename>&lt;conf_file&gt;</filename>
85 that corresponds to the <filename>opkg</filename> repository you have just created. 85 that corresponds to the <filename>opkg</filename> repository you have just created.
86 The following command forms should now work: 86 The following command forms should now work:
87 <literallayout class='monospaced'> 87 <literallayout class='monospaced'>
88 $ opkg-cl –f &lt;conf_file&gt; -o &lt;sysroot_dir&gt; update 88 $ opkg-cl –f &lt;conf_file&gt; -o &lt;sysroot_dir&gt; update