summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-01-06 15:13:34 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-03-08 12:07:36 -0800
commit39b508fb85c1079e40bd8b81fe9d85ab2cdda186 (patch)
tree062b5b4fdb039e078ec54b5d86f2f29becf12d06 /documentation
parentbc911b8af7cbc4dcfd9b0493a97e9fbd5d34b573 (diff)
downloadpoky-39b508fb85c1079e40bd8b81fe9d85ab2cdda186.tar.gz
documentation: Variables for docs and QS variablized
Beth has created a scheme that uses a file named "poky.ent" that contains a load of variables that can be used throughout the documents for releases. The variables can be set in the poky.ent file and then sucked in during the make process to specify a release. This commit adds the new file and the changes to the YP QS manual. (From yocto-docs rev: b08dde630a4f0762d8cc62c5579f6917d93ee854) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/poky.ent46
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml89
2 files changed, 91 insertions, 44 deletions
diff --git a/documentation/poky.ent b/documentation/poky.ent
new file mode 100644
index 0000000000..c2d0c02a6b
--- /dev/null
+++ b/documentation/poky.ent
@@ -0,0 +1,46 @@
1<!ENTITY DISTRO "1.1">
2<!ENTITY DISTRO_NAME "edison">
3<!ENTITY YOCTO_DOC_VERSION "latest">
4<!ENTITY POKYVERSION "6.0">
5<!ENTITY YOCTO_POKY "poky-&DISTRO_NAME;-&POKYVERSION;">
6<!ENTITY COPYRIGHT_YEAR "2010-2012">
7<!ENTITY YOCTO_DL_URL "http://downloads.yoctoproject.org">
8<!ENTITY YOCTO_HOME_URL "http://www.yoctoproject.org">
9<!ENTITY YOCTO_LISTS_URL "http://lists.yoctoproject.org">
10<!ENTITY YOCTO_BUGZILLA_URL "http://bugzilla.yoctoproject.org">
11<!ENTITY YOCTO_WIKI_URL "https://wiki.yoctoproject.org">
12<!ENTITY YOCTO_AB_URL "http://autobuilder.yoctoproject.org">
13<!ENTITY YOCTO_GIT_URL "http://git.yoctoproject.org">
14<!ENTITY YOCTO_ADTREPO_URL "http://adtrepo.yoctoproject.org">
15<!ENTITY OE_HOME_URL "http://www.openembedded.org">
16<!ENTITY OE_DOCS_URL "http://docs.openembedded.org">
17<!ENTITY BITBAKE_HOME_URL "http://developer.berlios.de/projects/bitbake/">
18<!ENTITY BITBAKE_DOCS_URL "http://bitbake.berlios.de/manual/">
19<!ENTITY ECLIPSE_MAIN_URL "http://www.eclipse.org/downloads">
20<!ENTITY ECLIPSE_DL_URL "http://download.eclipse.org">
21<!ENTITY ECLIPSE_UPDATES_URL "&ECLIPSE_DL_URL;/tm/updates/3.3">
22<!ENTITY ECLIPSE_INDIGO_URL "&ECLIPSE_DL_URL;/releases/indigo">
23<!ENTITY ECLIPSE_INDIGO_CDT_URL "&ECLIPSE_DL_URL;tools/cdt/releases/indigo">
24<!ENTITY YOCTO_DOCS_URL "&YOCTO_HOME_URL;/docs">
25<!ENTITY YOCTO_SOURCES_URL "&YOCTO_HOME_URL;/sources/">
26<!ENTITY YOCTO_AB_PORT_URL "&YOCTO_AB_URL;:8010">
27<!ENTITY YOCTO_AB_NIGHTLY_URL "&YOCTO_AB_URL;/nightly/">
28<!ENTITY YOCTO_POKY_URL "&YOCTO_DL_URL;/releases/poky/">
29<!ENTITY YOCTO_RELEASE_DL_URL "&YOCTO_DL_URL;/releases/yocto/yocto-&DISTRO;">
30<!ENTITY YOCTO_TOOLCHAIN_DL_URL "&YOCTO_RELEASE_DL_URL;/toolchain/">
31<!ENTITY YOCTO_ECLIPSE_DL_URL "&YOCTO_RELEASE_DL_URL;/eclipse-plugin/indigo;">
32<!ENTITY YOCTO_ADTINSTALLER_DL_URL "&YOCTO_RELEASE_DL_URL;/adt_installer">
33<!ENTITY YOCTO_POKY_DL_URL "&YOCTO_RELEASE_DL_URL;/&YOCTO_POKY;.tar.bz2">
34<!ENTITY YOCTO_MACHINES_DL_URL "&YOCTO_RELEASE_DL_URL;/machines">
35<!ENTITY YOCTO_QEMU_DL_URL "&YOCTO_MACHINES_DL_URL;/qemu">
36<!ENTITY YOCTO_PYTHON-i686_DL_URL "&YOCTO_DL_URL;/releases/miscsupport/yocto-&DISTRO;-python-nativesdk/python-nativesdk-standalone-i686.tar.bz2">
37<!ENTITY YOCTO_PYTHON-x86_64_DL_URL "&YOCTO_DL_URL;/releases/miscsupport/yocto-&DISTRO;-python-nativesdk/python-nativesdk-standalone-x86_64.tar.bz2">
38<!ENTITY YOCTO_DOCS_QS_URL "&YOCTO_DOCS_URL;/&YOCTO_DOC_VERSION;/yocto-project-qs/yocto-project-qs.html">
39<!ENTITY YOCTO_DOCS_ADT_URL "&YOCTO_DOCS_URL;/&YOCTO_DOC_VERSION;/adt-manual/adt-manual.html">
40<!ENTITY YOCTO_DOCS_REF_URL "&YOCTO_DOCS_URL;/&YOCTO_DOC_VERSION;/poky-ref-manual/poky-ref-manual.html">
41<!ENTITY YOCTO_DOCS_BSP_URL "&YOCTO_DOCS_URL;/&YOCTO_DOC_VERSION;/bsp-guide/bsp-guide.html">
42<!ENTITY YOCTO_DOCS_DEV_URL "&YOCTO_DOCS_URL;/&YOCTO_DOC_VERSION;/dev-manual/dev-manual.html">
43<!ENTITY YOCTO_DOCS_KERNEL_URL "&YOCTO_DOCS_URL;/&YOCTO_DOC_VERSION;/kernel-manual/kernel-manual.html">
44<!ENTITY YOCTO_ADTPATH_DIR "/opt/poky/&DISTRO;">
45<!ENTITY YOCTO_POKY_TARBALL "&YOCTO_POKY;.tar.bz2">
46<!ENTITY OE_INIT_PATH "&YOCTO_POKY;/oe-init-build-env">
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 0f2ecf4110..4f02b0a996 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -1,12 +1,13 @@
1<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 1<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> 2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
3[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
3 4
4<article id='intro'> 5<article id='intro'>
5 <imagedata fileref="figures/yocto-project-transp.png" width="6in" depth="1in" align="right" scale="25" /> 6 <imagedata fileref="figures/yocto-project-transp.png" width="6in" depth="1in" align="right" scale="25" />
6 7
7<section id='fake-title'> 8<section id='fake-title'>
8 <title>Yocto Project Quick Start</title> 9 <title>Yocto Project Quick Start</title>
9 <para>Copyright &copy; 2010-2011 Linux Foundation</para> 10 <para>Copyright &copy; &COPYRIGHT_YEAR; Linux Foundation</para>
10</section> 11</section>
11 12
12<section id='welcome'> 13<section id='welcome'>
@@ -28,24 +29,24 @@
28 </para> 29 </para>
29 <para> 30 <para>
30 For complete information on the Yocto Project, you should check out the 31 For complete information on the Yocto Project, you should check out the
31 <ulink url='http://www.yoctoproject.org'>Yocto Project Website</ulink>. 32 <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink>.
32 Through the website, you can find the latest builds, breaking news, full development 33 Through the website, you can find the latest builds, breaking news, full development
33 documentation, and a 34 documentation, and a
34 rich Yocto Project Development Community into which you can tap. 35 rich Yocto Project Development Community into which you can tap.
35 </para> 36 </para>
36 <para> 37 <para>
37 Finally, you might find the Frequently Asked Questions (FAQ) for the Yocto Project 38 Finally, you might find the Frequently Asked Questions (FAQ) for the Yocto Project
38 at <ulink url='https://wiki.yoctoproject.org/wiki/FAQ'>Yocto Project FAQ</ulink> and 39 at <ulink url='&YOCTO_WIKI_URL;/wiki/FAQ'>Yocto Project FAQ</ulink> and
39 the FAQ appendix located in 40 the FAQ appendix located in
40 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html'> 41 <ulink url='&YOCTO_DOCS_REF_URL;'>
41 The Yocto Project Reference Manual</ulink> helpful. 42 The Yocto Project Reference Manual</ulink> helpful.
42 </para> 43 </para>
43 <note> 44 <note>
44 Due to production processes, there could be differences between the Yocto Project 45 Due to production processes, there could be differences between the Yocto Project
45 documentation bundled in the release tarball and the 46 documentation bundled in the release tarball and the
46 <ulink url='http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html'> 47 <ulink url='&YOCTO_DOCS_QS_URL;'>
47 Yocto Project Quick Start</ulink> on 48 Yocto Project Quick Start</ulink> on
48 the <ulink url='http://www.yoctoproject.org'>Yocto Project</ulink> website. 49 the <ulink url='&YOCTO_HOME_URL;'>Yocto Project</ulink> website.
49 For the latest version of this manual, see the manual on the website. 50 For the latest version of this manual, see the manual on the website.
50 </note> 51 </note>
51</section> 52</section>
@@ -156,11 +157,11 @@
156 <listitem><para>openSUSE</para></listitem> 157 <listitem><para>openSUSE</para></listitem>
157 </itemizedlist> 158 </itemizedlist>
158 For a list of the distributions under validation and their status, see the 159 For a list of the distributions under validation and their status, see the
159 <ulink url='https://wiki.yoctoproject.org/wiki/Distribution_Support'>Distribution 160 <ulink url='&YOCTO_WIKI_URL;/wiki/Distribution_Support'>Distribution
160 Support</ulink> wiki page. 161 Support</ulink> wiki page.
161 <note> 162 <note>
162 For notes about using the Yocto Project on a RHEL 4-based host, see the 163 For notes about using the Yocto Project on a RHEL 4-based host, see the
163 <ulink url='https://wiki.yoctoproject.org/wiki/BuildingOnRHEL4'>BuildingOnRHEL4</ulink> 164 <ulink url='&YOCTO_WIKI_URL;/wiki/BuildingOnRHEL4'>BuildingOnRHEL4</ulink>
164 wiki page. 165 wiki page.
165 </note> 166 </note>
166 </para> 167 </para>
@@ -174,12 +175,12 @@
174 If you attempt to use a distribution not in the above list, you may or may not have success - you 175 If you attempt to use a distribution not in the above list, you may or may not have success - you
175 are venturing into untested territory. 176 are venturing into untested territory.
176 Refer to 177 Refer to
177 <ulink url='http://openembedded.net/index.php?title=OEandYourDistro&amp;action=historysubmit&amp;diff=4309&amp;okdid=4225'>OE and Your Distro</ulink> and 178 <ulink url='&OE_HOME_URL;/index.php?title=OEandYourDistro&amp;action=historysubmit&amp;diff=4309&amp;okdid=4225'>OE and Your Distro</ulink> and
178 <ulink url='http://openembedded.net/index.php?title=Required_software&amp;action=historysubmit&amp;diff=4311&amp;oldid=4251'>Required Software</ulink> 179 <ulink url='&OE_HOME_URL;/index.php?title=Required_software&amp;action=historysubmit&amp;diff=4311&amp;oldid=4251'>Required Software</ulink>
179 for information for other distributions used with the OpenEmbedded project, which might be 180 for information for other distributions used with the OpenEmbedded project, which might be
180 a starting point for exploration. 181 a starting point for exploration.
181 If you go down this path, you should expect problems. 182 If you go down this path, you should expect problems.
182 When you do, please go to <ulink url='http://bugzilla.yoctoproject.org'>Yocto Project Bugzilla</ulink> 183 When you do, please go to <ulink url='&YOCTO_BUGZILLA_URL;'>Yocto Project Bugzilla</ulink>
183 and submit a bug. 184 and submit a bug.
184 We are interested in hearing about your experience. 185 We are interested in hearing about your experience.
185 </para></note> 186 </para></note>
@@ -261,13 +262,13 @@
261 262
262 <para> 263 <para>
263 You can download the latest Yocto Project release by going to the 264 You can download the latest Yocto Project release by going to the
264 <ulink url="http://yoctoproject.org/download">Yocto Project Download page</ulink>. 265 <ulink url="&YOCTO_HOME_URL;/download">Yocto Project Download page</ulink>.
265 Just go to the page and click the "Yocto Downloads" link found in the "Download" 266 Just go to the page and click the "Yocto Downloads" link found in the "Download"
266 navigation pane to the right to view all available Yocto Project releases. 267 navigation pane to the right to view all available Yocto Project releases.
267 Then, click the "Yocto Release" link for the release you want from the list to 268 Then, click the "Yocto Release" link for the release you want from the list to
268 begin the download. 269 begin the download.
269 Nightly and developmental builds are also maintained at 270 Nightly and developmental builds are also maintained at
270 <ulink url="http://autobuilder.yoctoproject.org/nightly/"></ulink>. 271 <ulink url="&YOCTO_AB_NIGHTLY_URL;"></ulink>.
271 However, for this document a released version of Yocto Project is used. 272 However, for this document a released version of Yocto Project is used.
272 </para> 273 </para>
273 274
@@ -276,9 +277,9 @@
276 development system. 277 development system.
277 Doing so allows you to contribute back to the project. 278 Doing so allows you to contribute back to the project.
278 For information on how to get set up using this method, see the 279 For information on how to get set up using this method, see the
279 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#local-yp-release'>Yocto 280 "<ulink url='&YOCTO_DOCS_DEV_URL;#local-yp-release'>Yocto
280 Project Release</ulink>" item in 281 Project Release</ulink>" item in
281 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>The Yocto Project 282 <ulink url='&YOCTO_DOCS_DEV_URL;'>The Yocto Project
282 Development Manual</ulink>. 283 Development Manual</ulink>.
283 </para> 284 </para>
284 </section> 285 </section>
@@ -336,15 +337,15 @@
336 If you encounter problems with the Yocto Project finding and downloading source code, see 337 If you encounter problems with the Yocto Project finding and downloading source code, see
337 the FAQ entry "How does Poky obtain source code and will it work behind my 338 the FAQ entry "How does Poky obtain source code and will it work behind my
338 firewall or proxy server?" in 339 firewall or proxy server?" in
339 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html'> 340 <ulink url='&YOCTO_DOCS_REF_URL;'>
340 The Yocto Project Reference Manual</ulink>. 341 The Yocto Project Reference Manual</ulink>.
341 </para></note> 342 </para></note>
342 343
343 <para> 344 <para>
344 <literallayout class='monospaced'> 345 <literallayout class='monospaced'>
345 $ wget http://downloads.yoctoproject.org/releases/yocto/yocto-1.1/poky-edison-6.0.tar.bz2 346 $ wget &YOCTO_POKY_DL_URL;
346 $ tar xjf poky-edison-6.0.tar.bz2 347 $ tar xjf &YOCTO_POKY;.tar.bz2
347 $ source poky-edison-6.0/oe-init-build-env edison-6.0-build 348 $ source &OE_INIT_PATH; edison-6.0-build
348 </literallayout> 349 </literallayout>
349 </para> 350 </para>
350 351
@@ -364,7 +365,7 @@
364 release tarball from the source repositories using the 365 release tarball from the source repositories using the
365 <filename>wget</filename> command. 366 <filename>wget</filename> command.
366 Alternatively, you can go to the 367 Alternatively, you can go to the
367 <ulink url='http://www.yoctoproject.org/download'>Yocto Project website</ulink> 368 <ulink url='&YOCTO_HOME_URL;/download'>Yocto Project website</ulink>
368 Downloads page to retrieve the tarball.</para></listitem> 369 Downloads page to retrieve the tarball.</para></listitem>
369 <listitem><para>The second command extracts the files from the tarball and places 370 <listitem><para>The second command extracts the files from the tarball and places
370 them into a directory named <filename>poky-edison-6.0</filename> in the current 371 them into a directory named <filename>poky-edison-6.0</filename> in the current
@@ -397,8 +398,8 @@
397 398
398 <para> 399 <para>
399 Another couple of variables of interest are the 400 Another couple of variables of interest are the
400 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-BB_NUMBER_THREADS'><filename>BB_NUMBER_THREADS</filename></ulink> and the 401 <ulink url='&YOCTO_DOCS_REF_URL;#var-BB_NUMBER_THREADS'><filename>BB_NUMBER_THREADS</filename></ulink> and the
401 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-PARALLEL_MAKE'><filename>PARALLEL_MAKE</filename></ulink> variables. 402 <ulink url='&YOCTO_DOCS_REF_URL;#var-PARALLEL_MAKE'><filename>PARALLEL_MAKE</filename></ulink> variables.
402 By default, these variables are commented out. 403 By default, these variables are commented out.
403 However, if you have a multi-core CPU you might want to uncomment 404 However, if you have a multi-core CPU you might want to uncomment
404 the lines and set both variables equal to twice the number of your 405 the lines and set both variables equal to twice the number of your
@@ -411,10 +412,10 @@
411 the image. 412 the image.
412 By default, the Yocto Project build system uses the RPM package manager. 413 By default, the Yocto Project build system uses the RPM package manager.
413 You can control this configuration by using the 414 You can control this configuration by using the
414 <filename><ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink></filename> variable. 415 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink></filename> variable.
415 For additional package manager selection information, see 416 For additional package manager selection information, see
416 "<ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink>" in 417 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink>" in
417 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html'> 418 <ulink url='&YOCTO_DOCS_REF_URL;'>
418 The Yocto Project Reference Manual</ulink>. 419 The Yocto Project Reference Manual</ulink>.
419 </para> 420 </para>
420 421
@@ -423,15 +424,15 @@
423 <filename>core-image-sato</filename> in this example. 424 <filename>core-image-sato</filename> in this example.
424 For information on the <filename>-k</filename> option use the 425 For information on the <filename>-k</filename> option use the
425 <filename>bitbake --help</filename> command or see the 426 <filename>bitbake --help</filename> command or see the
426 "<ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#usingpoky-components-bitbake'>BitBake</ulink>" section in 427 "<ulink url='&YOCTO_DOCS_REF_URL;#usingpoky-components-bitbake'>BitBake</ulink>" section in
427 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html'>The Yocto Project Reference Manual</ulink>. 428 <ulink url='&YOCTO_DOCS_REF_URL;'>The Yocto Project Reference Manual</ulink>.
428 <literallayout class='monospaced'> 429 <literallayout class='monospaced'>
429 $ bitbake -k core-image-sato 430 $ bitbake -k core-image-sato
430 </literallayout> 431 </literallayout>
431 <note><para> 432 <note><para>
432 BitBake requires Python 2.6 or 2.7. For more information on this requirement, 433 BitBake requires Python 2.6 or 2.7. For more information on this requirement,
433 see the FAQ appendix in 434 see the FAQ appendix in
434 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html'> 435 <ulink url='&YOCTO_DOCS_REF_URL;'>
435 The Yocto Project Reference Manual</ulink>. 436 The Yocto Project Reference Manual</ulink>.
436 </para></note> 437 </para></note>
437 The final command runs the image: 438 The final command runs the image:
@@ -485,7 +486,7 @@
485 <para> 486 <para>
486 You can download the pre-built toolchain, which includes the <filename>runqemu</filename> 487 You can download the pre-built toolchain, which includes the <filename>runqemu</filename>
487 script and support files, from the appropriate directory under 488 script and support files, from the appropriate directory under
488 <ulink url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1/toolchain/'></ulink>. 489 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>.
489 Toolchains are available for 32-bit and 64-bit development systems from the 490 Toolchains are available for 32-bit and 64-bit development systems from the
490 <filename>i686</filename> and <filename>x86_64</filename> directories, respectively. 491 <filename>i686</filename> and <filename>x86_64</filename> directories, respectively.
491 Each type of development system supports five target architectures. 492 Each type of development system supports five target architectures.
@@ -513,7 +514,7 @@
513 </para> 514 </para>
514 515
515 <literallayout class='monospaced'> 516 <literallayout class='monospaced'>
516 poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2 517 poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2
517 </literallayout> 518 </literallayout>
518 519
519 <para> 520 <para>
@@ -526,15 +527,15 @@
526 <para> 527 <para>
527 <literallayout class='monospaced'> 528 <literallayout class='monospaced'>
528 $ cd / 529 $ cd /
529 $ sudo tar -xvjf ~/toolchains/poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2 530 $ sudo tar -xvjf ~/toolchains/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2
530 </literallayout> 531 </literallayout>
531 </para> 532 </para>
532 533
533 <para> 534 <para>
534 For more information on how to install tarballs, see the 535 For more information on how to install tarballs, see the
535 "<ulink url='http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball</ulink>" and 536 "<ulink url='&YOCTO_DOCS_ADT_URL;#using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball</ulink>" and
536 "<ulink url='http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-toolchain-from-within-the-build-tree'>Using BitBake and the Yocto Project Build Tree</ulink>" sections in 537 "<ulink url='&YOCTO_DOCS_ADT_URL;#using-the-toolchain-from-within-the-build-tree'>Using BitBake and the Yocto Project Build Tree</ulink>" sections in
537 <ulink url='http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html'>The Yocto Project 538 <ulink url='&YOCTO_DOCS_ADT_URL;'>The Yocto Project
538 Application Development Toolkit (ADT) User's Guide</ulink>. 539 Application Development Toolkit (ADT) User's Guide</ulink>.
539 </para> 540 </para>
540 </section> 541 </section>
@@ -544,7 +545,7 @@
544 545
545 <para> 546 <para>
546 You can download the pre-built Linux kernel suitable for running in the QEMU emulator from 547 You can download the pre-built Linux kernel suitable for running in the QEMU emulator from
547 <ulink url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1/machines/qemu'></ulink>. 548 <ulink url='&YOCTO_QEMU_DL_URL;'></ulink>.
548 Be sure to use the kernel that matches the architecture you want to simulate. 549 Be sure to use the kernel that matches the architecture you want to simulate.
549 Download areas exist for the five supported machine architectures: 550 Download areas exist for the five supported machine architectures:
550 <filename>qemuarm</filename>, <filename>qemumips</filename>, <filename>qemuppc</filename>, 551 <filename>qemuarm</filename>, <filename>qemumips</filename>, <filename>qemuppc</filename>,
@@ -565,8 +566,8 @@
565 566
566 <para> 567 <para>
567 You can learn more about downloading a Yocto Project kernel in the 568 You can learn more about downloading a Yocto Project kernel in the
568 "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#local-kernel-files'>Linux Yocto Kernel</ulink>" section of 569 "<ulink url='&YOCTO_DOCS_DEV_URL;#local-kernel-files'>Linux Yocto Kernel</ulink>" section of
569 <ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html'>The 570 <ulink url='&YOCTO_DOCS_DEV_URL;'>The
570 Yocto Project Development Manual</ulink>. 571 Yocto Project Development Manual</ulink>.
571 </para> 572 </para>
572 </section> 573 </section>
@@ -576,7 +577,7 @@
576 577
577 <para> 578 <para>
578 You can also download the filesystem image suitable for your target architecture from 579 You can also download the filesystem image suitable for your target architecture from
579 <ulink url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1/machines/qemu'></ulink>. 580 <ulink url='&YOCTO_QEMU_DL_URL;'></ulink>.
580 Again, be sure to use the filesystem that matches the architecture you want 581 Again, be sure to use the filesystem that matches the architecture you want
581 to simulate. 582 to simulate.
582 </para> 583 </para>
@@ -596,7 +597,7 @@
596 &lt;<emphasis>profile</emphasis>&gt; is the filesystem image's profile: 597 &lt;<emphasis>profile</emphasis>&gt; is the filesystem image's profile:
597 lsb, lsb-dev, lsb-sdk, lsb-qt3, minimal, minimal-dev, sato, sato-dev, or sato-sdk. 598 lsb, lsb-dev, lsb-sdk, lsb-qt3, minimal, minimal-dev, sato, sato-dev, or sato-sdk.
598 For information on these types of image profiles, see 599 For information on these types of image profiles, see
599 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink> in the Yocto Project Reference Manual. 600 <ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink> in the Yocto Project Reference Manual.
600 601
601 &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: 602 &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture:
602 x86, x86-64, ppc, mips, or arm. 603 x86, x86-64, ppc, mips, or arm.
@@ -611,7 +612,7 @@
611 Before you start the QEMU emulator, you need to set up the emulation environment. 612 Before you start the QEMU emulator, you need to set up the emulation environment.
612 The following command form sets up the emulation environment. 613 The following command form sets up the emulation environment.
613 <literallayout class='monospaced'> 614 <literallayout class='monospaced'>
614 $ source /opt/poky/1.1/environment-setup-&lt;<emphasis>arch</emphasis>&gt;-poky-linux-&lt;<emphasis>if</emphasis>&gt; 615 $ source &YOCTO_ADTPATH_DIR;/environment-setup-&lt;<emphasis>arch</emphasis>&gt;-poky-linux-&lt;<emphasis>if</emphasis>&gt;
615 616
616 Where: 617 Where:
617 &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: 618 &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture:
@@ -644,8 +645,8 @@
644 This example assumes the root filesystem tarball has been downloaded and expanded, and 645 This example assumes the root filesystem tarball has been downloaded and expanded, and
645 that the kernel and filesystem are for a 32-bit target architecture. 646 that the kernel and filesystem are for a 32-bit target architecture.
646 <literallayout class='monospaced'> 647 <literallayout class='monospaced'>
647 $ source /opt/poky/1.1/environment-setup-i686-poky-linux 648 $ source &YOCTO_ADTPATH_DIR;/environment-setup-i686-poky-linux
648 $ runqemu qemux86 bzImage-3.0-qemux86-1.1.bin \ 649 $ runqemu qemux86 bzImage-3.0-qemux86-&DISTRO;.bin \
649 core-image-sato-qemux86.ext3 650 core-image-sato-qemux86.ext3
650 </literallayout> 651 </literallayout>
651 </para> 652 </para>