summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-06-13 09:12:08 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-06-29 14:59:22 +0100
commit6c9c0f1f45d8eca2e8a91487528b79f068499e50 (patch)
tree9047e15661665c6b086546f1bb05d1609bfeec89 /documentation
parent8650364e50db190996206341afb56c175803fde6 (diff)
downloadpoky-6c9c0f1f45d8eca2e8a91487528b79f068499e50.tar.gz
documentation/poky-ref-manual/faq.xml: 1.1.2 variables and updates
First pass of implementing the poky.ent variables. Also, applied obvious type fixes. (From yocto-docs rev: 5f5d3735bea5db12847dc9b9fa01aee0f5dc2b41) 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-ref-manual/faq.xml31
1 files changed, 16 insertions, 15 deletions
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml
index 669b2d5aa5..61853b5120 100644
--- a/documentation/poky-ref-manual/faq.xml
+++ b/documentation/poky-ref-manual/faq.xml
@@ -1,5 +1,6 @@
1<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 1<!DOCTYPE appendix 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<appendix id='faq'> 5<appendix id='faq'>
5<title>FAQ</title> 6<title>FAQ</title>
@@ -7,13 +8,13 @@
7 <qandaentry> 8 <qandaentry>
8 <question> 9 <question>
9 <para> 10 <para>
10 How does Poky differ from <ulink url='http://www.openembedded.org/'>OpenEmbedded</ulink>? 11 How does Poky differ from <ulink url='&OE_HOME_URL;'>OpenEmbedded</ulink>?
11 </para> 12 </para>
12 </question> 13 </question>
13 <answer> 14 <answer>
14 <para> 15 <para>
15 Poky is the Yocto Project build system that was derived from <ulink 16 Poky is the Yocto Project build system that was derived from <ulink
16 url='http://www.openembedded.org/'>OpenEmbedded</ulink>. 17 url='&OE_HOME_URL;'>OpenEmbedded</ulink>.
17 Poky is a stable, smaller subset focused on the mobile environment. 18 Poky is a stable, smaller subset focused on the mobile environment.
18 Development in the Yocto Project using Poky is closely tied to OpenEmbedded with 19 Development in the Yocto Project using Poky is closely tied to OpenEmbedded with
19 features being merged regularly between the two for mutual benefit. 20 features being merged regularly between the two for mutual benefit.
@@ -33,8 +34,8 @@
33 You can use a stand-alone tarball to provide Python 2.6. 34 You can use a stand-alone tarball to provide Python 2.6.
34 You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations: 35 You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations:
35 <itemizedlist> 36 <itemizedlist>
36 <listitem><para><ulink url='http://downloads.yoctoproject.org/releases/miscsupport/yocto-1.0-python-nativesdk/python-nativesdk-standalone-i686.tar.bz2'>32-bit tarball</ulink></para></listitem> 37 <listitem><para><ulink url='&YOCTO_PYTHON-i686_DL_URL;'>32-bit tarball</ulink></para></listitem>
37 <listitem><para><ulink url='http://downloads.yoctoproject.org/releases/miscsupport/yocto-1.0-python-nativesdk/python-nativesdk-standalone-x86_64.tar.bz2'>64-bit tarball</ulink></para></listitem> 38 <listitem><para><ulink url='&YOCTO_PYTHON-x86_64_DL_URL;'>64-bit tarball</ulink></para></listitem>
38 </itemizedlist> 39 </itemizedlist>
39 </para> 40 </para>
40 <para> 41 <para>
@@ -139,7 +140,7 @@
139 <para> 140 <para>
140 To add a package, you need to create a BitBake recipe. 141 To add a package, you need to create a BitBake recipe.
141 For information on how to add a package, see the 142 For information on how to add a package, see the
142 <link linkend='usingpoky-extend-addpkg'>Adding a Package</link> section 143 "<link linkend='usingpoky-extend-addpkg'>Adding a Package</link>" section
143 earlier in this manual. 144 earlier in this manual.
144 </para> 145 </para>
145 </answer> 146 </answer>
@@ -171,7 +172,7 @@
171 </question> 172 </question>
172 <answer> 173 <answer>
173 <para> 174 <para>
174 <ulink url='http://www.gnome.org/mobile/'>GNOME Mobile</ulink> is a subset of the GNOME 175 GNOME Mobile is a subset of the <ulink url='http://www.gnome.org'>GNOME</ulink>
175 platform targeted at mobile and embedded devices. 176 platform targeted at mobile and embedded devices.
176 The the main difference between GNOME Mobile and standard GNOME is that 177 The the main difference between GNOME Mobile and standard GNOME is that
177 desktop-orientated libraries have been removed, along with deprecated libraries, 178 desktop-orientated libraries have been removed, along with deprecated libraries,
@@ -385,9 +386,9 @@
385 </question> 386 </question>
386 <answer> 387 <answer>
387 <para> 388 <para>
388 You need to create a form factor file as described in 389 You need to create a form factor file as described in the
389 <xref linkend='bsp-filelayout-misc-recipes'>"Miscellaneous Recipe Files"</xref> 390 "<link linkend='bsp-filelayout-misc-recipes'>Miscellaneous Recipe Files</link>"
390 and set the <filename>HAVE_TOUCHSCREEN</filename> variable equal to one as follows: 391 section and set the <filename>HAVE_TOUCHSCREEN</filename> variable equal to one as follows:
391 <literallayout class='monospaced'> 392 <literallayout class='monospaced'>
392 HAVE_TOUCHSCREEN=1 393 HAVE_TOUCHSCREEN=1
393 </literallayout> 394 </literallayout>
@@ -407,8 +408,8 @@
407 automatically bring up network interfaces. 408 automatically bring up network interfaces.
408 Therefore, you will need to add a BSP-specific netbase that includes an interfaces 409 Therefore, you will need to add a BSP-specific netbase that includes an interfaces
409 file. 410 file.
410 See <xref linkend='bsp-filelayout-misc-recipes'>"Miscellaneous Recipe Files"</xref> 411 See the "<link linkend='bsp-filelayout-misc-recipes'>Miscellaneous Recipe Files</link>"
411 for information on creating these types of miscellaneous recipe files. 412 section for information on creating these types of miscellaneous recipe files.
412 </para> 413 </para>
413 <para> 414 <para>
414 For example, add the following files to your layer: 415 For example, add the following files to your layer:
@@ -493,8 +494,8 @@
493 494
494 <qandaentry> 495 <qandaentry>
495 <question> 496 <question>
496 <para> 497 <para id='how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'>
497 How does the Yocto Project obtain source code and will it work behind my 498 How does the Yocto Project build system obtain source code and will it work behind my
498 firewall or proxy server? 499 firewall or proxy server?
499 </para> 500 </para>
500 </question> 501 </question>
@@ -573,7 +574,7 @@
573 any network accesses to anything other than the PREMIRROR would fail. 574 any network accesses to anything other than the PREMIRROR would fail.
574 </para> 575 </para>
575 <para> 576 <para>
576 Poky also honors the standard environment variables 577 Poky also honors the standard shell environment variables
577 <filename>http_proxy</filename>, <filename>ftp_proxy</filename>, 578 <filename>http_proxy</filename>, <filename>ftp_proxy</filename>,
578 <filename>https_proxy</filename>, and <filename>all_proxy</filename> 579 <filename>https_proxy</filename>, and <filename>all_proxy</filename>
579 to redirect requests through proxy servers. 580 to redirect requests through proxy servers.