sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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>
This commit is contained in:
Scott Rifenbark 2011-08-15 07:42:38 -07:00 committed by Richard Purdie
parent d5d0f08c32
commit 7946934811
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
documentation/adt-manual/adt-package.xml
View File

@ -4,9 +4,9 @@
<chapter id='adt-package'> <chapter id='adt-package'>
<title>Optionally Customizing the Development Packages Installation</title> <title>Optionally Customizing the Development Packages Installation</title>
<para> <para>
Because the Yocto Project is suited for embedded Linux development it is Because the Yocto Project is suited for embedded Linux development, it is
likely that you will need to customize your development packages installation. 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 For example, if you are developing a minimal image, then you might not need
certain packages (e.g. graphics support packages). certain packages (e.g. graphics support packages).
Thus, you would like to be able to remove those packages from your target sysroot. Thus, you would like to be able to remove those packages from your target sysroot.
</para> </para>
@ -40,7 +40,7 @@
<section id='configuring-the-pms'> <section id='configuring-the-pms'>
<title>Configuring the PMS</title> <title>Configuring the PMS</title>
<para> <para>
Whichever PMS you are using you need to be sure that the Whichever PMS you are using, you need to be sure that the
<filename>PACKAGE_CLASSES</filename> variable in the <filename>conf/local.conf</filename> <filename>PACKAGE_CLASSES</filename> variable in the <filename>conf/local.conf</filename>
file is set to reflect that system. file is set to reflect that system.
The first value you choose for the variable specifies the package file format for the root The first value you choose for the variable specifies the package file format for the root
@ -53,8 +53,9 @@
the <filename>libglade</filename> package to the target sysroot. the <filename>libglade</filename> package to the target sysroot.
</para> </para>
<para> <para>
First, you should generate the ipk file for the <filename>libglade</filename> package and add it First, you should generate the <filename>ipk</filename> file for the
into a working opkg repository. <filename>libglade</filename> package and add it
into a working <filename>opkg</filename> repository.
Use these commands: Use these commands:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake libglade $ bitbake libglade
@ -62,11 +63,11 @@
</literallayout> </literallayout>
</para> </para>
<para> <para>
Next, source the environment setup script found in the Yocto Project source directory. Next, source the environment setup script found in the Yocto Project files.
Follow that by setting up the installation destination to point to your Follow that by setting up the installation destination to point to your
sysroot as <filename>&lt;sysroot_dir&gt;</filename>. sysroot as <filename>&lt;sysroot_dir&gt;</filename>.
Finally, have an opkg configuration file <filename>&lt;conf_file&gt;</filename> Finally, have an <filename>opkg</filename> configuration file <filename>&lt;conf_file&gt;</filename>
that corresponds to the opkg repository you have just created. that corresponds to the <filename>opkg</filename> repository you have just created.
The following command forms should now work: The following command forms should now work:
<literallayout class='monospaced'> <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; update