documentation/adt-manual/adt-package.xml: Edits to packaging chapter

Some minor edits to create some links to some terms used.

(From yocto-docs rev: 1559b8caca07cce8630de9ddf8c84f0b24fa35e7)

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 2012-07-17 14:14:59 -07:00 committed by Richard Purdie
parent bd456271e4
commit 14554f8d2e
1 changed files with 6 additions and 3 deletions

View File

@ -45,7 +45,8 @@
<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> <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink>
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
filesystem at sysroot. filesystem at sysroot.
@ -55,7 +56,8 @@
<note> <note>
For build performance information related to the PMS, see For build performance information related to the PMS, see
<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink> in The Yocto Project Reference Manual. <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink>
in the Yocto Project Reference Manual.
</note> </note>
<para> <para>
@ -75,7 +77,8 @@
</para> </para>
<para> <para>
Next, source the environment setup script found in the source directory. Next, source the environment setup script found in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>.
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 OPKG configuration file <filename>&lt;conf_file&gt;</filename>