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>
This commit is contained in:
Scott Rifenbark 2011-06-23 09:58:35 -07:00 committed by Richard Purdie
parent 5a55f7f4dc
commit c655092dea
1 changed files with 11 additions and 11 deletions

View File

@ -8,7 +8,7 @@
likely that you will need to customize your development packages installation.
For example, if you are developing a minimal image then you might not need
certain packages (e.g. graphics support packages).
Thus, you would like to be able to remove those packages from your sysroot.
Thus, you would like to be able to remove those packages from your target sysroot.
</para>
<section id='package-management-systems'>
@ -44,16 +44,16 @@
<filename>PACKAGE_CLASSES</filename> variable in the <filename>conf/local.conf</filename>
file is set to reflect that system.
The first value you choose for the variable specifies the package file format for the root
filesystem.
filesystem at sysroot.
Additional values specify additional formats for convenience or testing.
See the configuration file for details.
</para>
<para>
As an example, consider a scenario where you are using OPKG and you want to add
the libglade package to sysroot.
the <filename>libglade</filename> package to the target sysroot.
</para>
<para>
First, you should generate the ipk file for the libglade package and add it
First, you should generate the ipk file for the <filename>libglade</filename> package and add it
into a working opkg repository.
Use these commands:
<literallayout class='monospaced'>
@ -62,17 +62,17 @@
</literallayout>
</para>
<para>
Next, source the environment setup script.
Next, source the environment setup script found in the Yocto Project source directory.
Follow that by setting up the installation destination to point to your
sysroot as <filename>&lt;sysroot dir&gt;</filename>.
Finally, have an opkg configuration file <filename>&lt;conf file&gt;</filename>
sysroot as <filename>&lt;sysroot_dir&gt;</filename>.
Finally, have an opkg configuration file <filename>&lt;conf_file&gt;</filename>
that corresponds to the opkg repository you have just created.
The following command forms should now work:
<literallayout class='monospaced'>
$ opkg-cl f &lt;conf file&gt; -o &lt;sysroot dir&gt; update
$ opkg-cl f &lt;conf file&gt;> -o &lt;sysroot dir&gt; --force-overwrite install libglade
$ opkg-cl f &lt;conf file&gt; -o &lt;sysroot dir&gt; --force-overwrite install libglade-dbg
$ opkg-cl f &lt;conf file&gt; -o &lt;sysroot dir&gt; --force-overwrite install libglade-dev
$ opkg-cl f &lt;conf_file&gt; -o &lt;sysroot-dir&gt; update
$ opkg-cl f &lt;cconf_file&gt;> -o &lt;sysroot-dir&gt; --force-overwrite install libglade
$ opkg-cl f &lt;cconf_file&gt; -o &lt;sysroot-dir&gt; --force-overwrite install libglade-dbg
$ opkg-cl f &lt;conf_file&gt; -o &lt;sysroot-dir&gt; --force-overwrite install libglade-dev
</literallayout>
</para>
</section>