diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-08-15 07:42:38 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-08-20 17:52:00 -0700 |
commit | 794693481102f88318bd11be109390ba0b44dcd8 (patch) | |
tree | cf78587a4b6555f02956c07cc4ae220d1cb3bb68 /documentation/adt-manual/adt-package.xml | |
parent | d5d0f08c3232c1d27194b8380b924a5dd2c245e5 (diff) | |
download | poky-794693481102f88318bd11be109390ba0b44dcd8.tar.gz |
documentation/adt-manual/adt-package.xml: Minor edits
(From yocto-docs rev: f035bf540c07b98d88dbf134b4a4706887754e32)
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.xml | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml index 9f982d13ad..77c5d96462 100644 --- a/documentation/adt-manual/adt-package.xml +++ b/documentation/adt-manual/adt-package.xml | |||
@@ -4,9 +4,9 @@ | |||
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 | <para> | 6 | <para> |
7 | Because the Yocto Project is suited for embedded Linux development it is | 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. | 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 | 9 | For example, if you are developing a minimal image, then you might not need |
10 | certain packages (e.g. graphics support packages). | 10 | certain packages (e.g. graphics support packages). |
11 | Thus, you would like to be able to remove those packages from your target sysroot. | 11 | Thus, you would like to be able to remove those packages from your target sysroot. |
12 | </para> | 12 | </para> |
@@ -40,7 +40,7 @@ | |||
40 | <section id='configuring-the-pms'> | 40 | <section id='configuring-the-pms'> |
41 | <title>Configuring the PMS</title> | 41 | <title>Configuring the PMS</title> |
42 | <para> | 42 | <para> |
43 | Whichever PMS you are using you need to be sure that the | 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> | 44 | <filename>PACKAGE_CLASSES</filename> variable in the <filename>conf/local.conf</filename> |
45 | file is set to reflect that system. | 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 | 46 | The first value you choose for the variable specifies the package file format for the root |
@@ -53,8 +53,9 @@ | |||
53 | the <filename>libglade</filename> package to the target sysroot. | 53 | the <filename>libglade</filename> package to the target sysroot. |
54 | </para> | 54 | </para> |
55 | <para> | 55 | <para> |
56 | First, you should generate the ipk file for the <filename>libglade</filename> package and add it | 56 | First, you should generate the <filename>ipk</filename> file for the |
57 | into a working opkg repository. | 57 | <filename>libglade</filename> package and add it |
58 | into a working <filename>opkg</filename> repository. | ||
58 | Use these commands: | 59 | Use these commands: |
59 | <literallayout class='monospaced'> | 60 | <literallayout class='monospaced'> |
60 | $ bitbake libglade | 61 | $ bitbake libglade |
@@ -62,11 +63,11 @@ | |||
62 | </literallayout> | 63 | </literallayout> |
63 | </para> | 64 | </para> |
64 | <para> | 65 | <para> |
65 | Next, source the environment setup script found in the Yocto Project source directory. | 66 | Next, source the environment setup script found in the Yocto Project files. |
66 | Follow that by setting up the installation destination to point to your | 67 | Follow that by setting up the installation destination to point to your |
67 | sysroot as <filename><sysroot_dir></filename>. | 68 | sysroot as <filename><sysroot_dir></filename>. |
68 | Finally, have an opkg configuration file <filename><conf_file></filename> | 69 | Finally, have an <filename>opkg</filename> configuration file <filename><conf_file></filename> |
69 | that corresponds to the opkg repository you have just created. | 70 | that corresponds to the <filename>opkg</filename> repository you have just created. |
70 | The following command forms should now work: | 71 | The following command forms should now work: |
71 | <literallayout class='monospaced'> | 72 | <literallayout class='monospaced'> |
72 | $ opkg-cl –f <conf_file> -o <sysroot-dir> update | 73 | $ opkg-cl –f <conf_file> -o <sysroot-dir> update |