diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-06-23 09:58:35 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-06-24 11:27:43 +0100 |
commit | c655092deac15099c9d324b8dbc1d18cea288651 (patch) | |
tree | 38dc546a09b85ed055fb44468db1f543b9753e33 | |
parent | 5a55f7f4dc79ac0e1049ac3240195ec56a0bf315 (diff) | |
download | poky-c655092deac15099c9d324b8dbc1d18cea288651.tar.gz |
documentation/adt-manual/adt-package.xml: Updates to configuring PMS
Changed the command examples so the variables contained underscore
characters.
(From yocto-docs rev: 34bfceb14a04c5fa026486f33d32df7c21f8c742)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r-- | documentation/adt-manual/adt-package.xml | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml index 96c2b59ba9..9f982d13ad 100644 --- a/documentation/adt-manual/adt-package.xml +++ b/documentation/adt-manual/adt-package.xml | |||
@@ -8,7 +8,7 @@ | |||
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 sysroot. | 11 | Thus, you would like to be able to remove those packages from your target sysroot. |
12 | </para> | 12 | </para> |
13 | 13 | ||
14 | <section id='package-management-systems'> | 14 | <section id='package-management-systems'> |
@@ -44,16 +44,16 @@ | |||
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 |
47 | filesystem. | 47 | filesystem at sysroot. |
48 | Additional values specify additional formats for convenience or testing. | 48 | Additional values specify additional formats for convenience or testing. |
49 | See the configuration file for details. | 49 | See the configuration file for details. |
50 | </para> | 50 | </para> |
51 | <para> | 51 | <para> |
52 | As an example, consider a scenario where you are using OPKG and you want to add | 52 | As an example, consider a scenario where you are using OPKG and you want to add |
53 | the libglade package to 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 libglade package and add it | 56 | First, you should generate the ipk file for the <filename>libglade</filename> package and add it |
57 | into a working opkg repository. | 57 | into a working opkg repository. |
58 | Use these commands: | 58 | Use these commands: |
59 | <literallayout class='monospaced'> | 59 | <literallayout class='monospaced'> |
@@ -62,17 +62,17 @@ | |||
62 | </literallayout> | 62 | </literallayout> |
63 | </para> | 63 | </para> |
64 | <para> | 64 | <para> |
65 | Next, source the environment setup script. | 65 | Next, source the environment setup script found in the Yocto Project source directory. |
66 | Follow that by setting up the installation destination to point to your | 66 | Follow that by setting up the installation destination to point to your |
67 | sysroot as <filename><sysroot dir></filename>. | 67 | sysroot as <filename><sysroot_dir></filename>. |
68 | Finally, have an opkg configuration file <filename><conf file></filename> | 68 | Finally, have an opkg configuration file <filename><conf_file></filename> |
69 | that corresponds to the opkg repository you have just created. | 69 | that corresponds to the opkg repository you have just created. |
70 | The following command forms should now work: | 70 | The following command forms should now work: |
71 | <literallayout class='monospaced'> | 71 | <literallayout class='monospaced'> |
72 | $ opkg-cl –f <conf file> -o <sysroot dir> update | 72 | $ opkg-cl –f <conf_file> -o <sysroot-dir> update |
73 | $ opkg-cl –f <conf file>> -o <sysroot dir> --force-overwrite install libglade | 73 | $ opkg-cl –f <cconf_file>> -o <sysroot-dir> --force-overwrite install libglade |
74 | $ opkg-cl –f <conf file> -o <sysroot dir> --force-overwrite install libglade-dbg | 74 | $ opkg-cl –f <cconf_file> -o <sysroot-dir> --force-overwrite install libglade-dbg |
75 | $ opkg-cl –f <conf file> -o <sysroot dir> --force-overwrite install libglade-dev | 75 | $ opkg-cl –f <conf_file> -o <sysroot-dir> --force-overwrite install libglade-dev |
76 | </literallayout> | 76 | </literallayout> |
77 | </para> | 77 | </para> |
78 | </section> | 78 | </section> |