documentation/poky-ref-manual/extendpoky.xml: 1.1.2 variables and updates

First pass at implementing the poky.ent variables.  Also corrected
some text ares.

(From yocto-docs rev: fa1714d3ebf569b19d48667c592126b6c4b445c3)

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-06-14 06:49:19 -07:00
committed by Richard Purdie
parent c8fc8aa4ae
commit fcf7db01c0

View File

@@ -1,5 +1,6 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
<chapter id='extendpoky'> <chapter id='extendpoky'>
@@ -24,7 +25,7 @@
variables. variables.
For information on variables that are useful for recipes and for information about recipe naming For information on variables that are useful for recipes and for information about recipe naming
issues, see the issues, see the
<link linkend='ref-varlocality-recipe-required'>Required</link> section for recipe variables. "<link linkend='ref-varlocality-recipe-required'>Required</link>" section for recipe variables.
</para> </para>
<para> <para>
@@ -114,7 +115,7 @@
<para> <para>
The variable <filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link> The variable <filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link>
</filename> is used to track source license changes as described in the </filename> is used to track source license changes as described in the
<link linkend='usingpoky-configuring-LIC_FILES_CHKSUM'>Track License Change</link> "<link linkend='usingpoky-configuring-LIC_FILES_CHKSUM'>Track License Change</link>"
section. section.
You can quickly create Autotool-based recipes in a manner similar to the previous example. You can quickly create Autotool-based recipes in a manner similar to the previous example.
</para> </para>
@@ -532,10 +533,9 @@
<para> <para>
For a complete example that shows how to add a new machine to the Yocto Project, For a complete example that shows how to add a new machine to the Yocto Project,
see the see the
<ulink url='http://www.yoctoproject.org/docs/1.1.1/dev-manual/dev-manual.html#dev-manual-bsp-appendix'> <ulink url='&YOCTO_DOCS_DEV_URL;#dev-manual-bsp-appendix'>
BSP Development Example</ulink> in Appendix A of BSP Development Example</ulink> in Appendix A of
<ulink url='http://www.yoctoproject.org/docs/1.1.1/dev-manual/dev-manual.html'> The Yocto Project Development Manual.
The Yocto Project Development Manual</ulink>.
</para> </para>
<section id="platdev-newmachine-conffile"> <section id="platdev-newmachine-conffile">
@@ -786,7 +786,7 @@
<para> <para>
This section overviews the Multilib process only. This section overviews the Multilib process only.
For more details on how to implement Multilib, see the For more details on how to implement Multilib, see the
<ulink url='https://wiki.yoctoproject.org/wiki/Multilib'>Multilib</ulink> wiki <ulink url='&YOCTO_WIKI_URL;/wiki/Multilib'>Multilib</ulink> wiki
page. page.
</para> </para>
@@ -1321,7 +1321,7 @@
Experience shows that buildbot is a good fit for this role. Experience shows that buildbot is a good fit for this role.
What works well is to configure buildbot to make two types of builds: What works well is to configure buildbot to make two types of builds:
incremental and full (from scratch). incremental and full (from scratch).
See <ulink url='http://www.yoctoproject.org:8010'>the buildbot for the See <ulink url='&YOCTO_HOME_URL;:8010'>the buildbot for the
Yocto Project</ulink> for an example implementation that uses buildbot. Yocto Project</ulink> for an example implementation that uses buildbot.
</para> </para>