summaryrefslogtreecommitdiffstats
path: root/handbook/faq.xml
diff options
context:
space:
mode:
Diffstat (limited to 'handbook/faq.xml')
-rw-r--r--handbook/faq.xml234
1 files changed, 234 insertions, 0 deletions
diff --git a/handbook/faq.xml b/handbook/faq.xml
new file mode 100644
index 0000000000..2c227bfc62
--- /dev/null
+++ b/handbook/faq.xml
@@ -0,0 +1,234 @@
1<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
3
4<appendix id='faq'>
5<title>FAQ</title>
6<qandaset>
7 <qandaentry>
8 <question>
9 <para>
10 How does Poky differ from <ulink url='http://www.openembedded.org/'>OpenEmbedded</ulink>?
11 </para>
12 </question>
13 <answer>
14 <para>
15 Poky is a derivative of <ulink
16 url='http://www.openembedded.org/'>OpenEmbedded</ulink>, a stable,
17 smaller subset focused on the GNOME Mobile environment. Development
18 in Poky is closely tied to OpenEmbedded with features being merged
19 regularly between the two for mutual benefit.
20 </para>
21 </answer>
22 </qandaentry>
23 <qandaentry>
24 <question>
25 <para>
26 How can you claim Poky is stable?
27 </para>
28 </question>
29 <answer>
30 <para>
31 There are three areas that help with stability;
32
33 <itemizedlist>
34 <listitem>
35 <para>
36 We keep Poky small and focused - around 650 packages compared to over 5000 for full OE
37 </para>
38 </listitem>
39 <listitem>
40 <para>
41 We only support hardware that we have access to for testing
42 </para>
43 </listitem>
44 <listitem>
45 <para>
46 We have a Buildbot which provides continuous build and integration tests
47 </para>
48 </listitem>
49 </itemizedlist>
50 </para>
51 </answer>
52 </qandaentry>
53 <qandaentry>
54 <question>
55 <para>
56 How do I get support for my board added to Poky?
57 </para>
58 </question>
59 <answer>
60 <para>
61 There are two main ways to get a board supported in Poky;
62 <itemizedlist>
63 <listitem>
64 <para>
65 Send us the board if we don't have it yet
66 </para>
67 </listitem>
68 <listitem>
69 <para>
70 Send us bitbake recipes if you have them (see the Poky handbook to find out how to create recipes)
71 </para>
72 </listitem>
73 </itemizedlist>
74 Usually if it's not a completely exotic board then adding support in Poky should be fairly straightforward.
75 </para>
76 </answer>
77 </qandaentry>
78 <qandaentry>
79 <question>
80 <para>
81 Are there any products running poky ?
82 </para>
83 </question>
84 <answer>
85 <para>
86 The <ulink url='http://vernier.com/labquest/'>Vernier Labquest</ulink> is using Poky (for more about the Labquest see the case study at OpenedHand). There are a number of pre-production devices using Poky and we will announce those as soon as they are released.
87 </para>
88 </answer>
89 </qandaentry>
90 <qandaentry>
91 <question>
92 <para>
93 What is the Poky output ?
94 </para>
95 </question>
96 <answer>
97 <para>
98 The output of a Poky build will depend on how it was started, as the same set of recipes can be used to output various formats. Usually the output is a flashable image ready for the target device.
99 </para>
100 </answer>
101 </qandaentry>
102 <qandaentry>
103 <question>
104 <para>
105 How do I add my package to Poky?
106 </para>
107 </question>
108 <answer>
109 <para>
110 To add a package you need to create a bitbake recipe - see the Poky handbook to find out how to create a recipe.
111 </para>
112 </answer>
113 </qandaentry>
114 <qandaentry>
115 <question>
116 <para>
117 Do I have to reflash my entire board with a new poky image when recompiling a package?
118 </para>
119 </question>
120 <answer>
121 <para>
122 Poky can build packages in various formats, ipkg, Debian package, or RPM. The package can then be upgraded using the package tools on the device, much like on a desktop distribution like Ubuntu or Fedora.
123 </para>
124 </answer>
125 </qandaentry>
126 <qandaentry>
127 <question>
128 <para>
129 What is GNOME Mobile? What's the difference between GNOME Mobile and GNOME?
130 </para>
131 </question>
132 <answer>
133 <para>
134 <ulink url='http://www.gnome.org/mobile/'>GNOME Mobile</ulink> is a subset of the GNOME platform targeted at mobile and embedded devices. The the main difference between GNOME Mobile and standard GNOME is that desktop-orientated libraries have been removed, along with deprecated libraries, creating a much smaller footprint.
135 </para>
136 </answer>
137 </qandaentry>
138 <qandaentry>
139 <question>
140 <para>
141 How do I make Poky work in RHEL/CentOS?
142 </para>
143 </question>
144 <answer>
145 <para>
146 To get Poky working under RHEL/CentOS 5.1 you need to first install some required packages. The standard CentOS packages needed are:
147 <itemizedlist>
148 <listitem>
149 <para>
150 "Development tools" (selected during installation)
151 </para>
152 </listitem>
153 <listitem>
154 <para>
155 texi2html
156 </para>
157 </listitem>
158 <listitem>
159 <para>
160 compat-gcc-34
161 </para>
162 </listitem>
163 </itemizedlist>
164 </para>
165
166 <para>
167 On top of those the following external packages are needed:
168 <itemizedlist>
169 <listitem>
170 <para>
171 python-sqlite2 from <ulink
172 url='http://dag.wieers.com/rpm/packages/python-sqlite2/'>DAG
173 repository</ulink>
174 </para>
175 </listitem>
176 <listitem>
177 <para>
178 help2man from <ulink
179 url='http://centos.karan.org/el5/extras/testing/i386/RPMS/help2man-1.33.1-2.noarch.rpm'>Karan
180 repository</ulink>
181 </para>
182 </listitem>
183 </itemizedlist>
184 </para>
185
186 <para>
187 Once these packages are installed Poky will be able to build standard images however there
188 may be a problem with QEMU segfaulting. You can either disable the generation of binary
189 locales by setting <glossterm><link linkend='var-ENABLE_BINARY_LOCALE_GENERATION'>ENABLE_BINARY_LOCALE_GENERATION</link>
190 </glossterm> to "0" or remove the linux-2.6-execshield.patch from the kernel and rebuild
191 it since its that patch which causes the problems with QEMU.
192 </para>
193 </answer>
194 </qandaentry>
195 <qandaentry>
196 <question>
197 <para>
198 I see lots of 404 responses for files on http://folks.o-hand.com/~richard/poky/sources/*. Is something wrong?
199 </para>
200 </question>
201 <answer>
202 <para>
203 Nothing is wrong, Poky will check any configured source mirrors before downloading
204 from the upstream sources. It does this searching for both source archives and
205 pre-checked out versions of SCM managed software. This is so in large installations,
206 it can reduce load on the SCM servers themselves. The address above is one of the
207 default mirrors configured into standard Poky so if an upstream source disappears,
208 we can place sources there so builds continue to work.
209 </para>
210 </answer>
211 </qandaentry>
212 <qandaentry>
213 <question>
214 <para>
215 I have a machine specific data in a package for one machine only but the package is
216 being marked as machine specific in all cases, how do I stop it?
217 </para>
218 </question>
219 <answer>
220 <para>
221 Set <glossterm><link linkend='var-SRC_URI_OVERRIDES_PACKAGE_ARCH'>SRC_URI_OVERRIDES_PACKAGE_ARCH</link>
222 </glossterm> = "0" in the .bb file but make sure the package is manually marked as
223 machine specific in the case that needs it. The code which handles <glossterm><link
224 linkend='var-SRC_URI_OVERRIDES_PACKAGE_ARCH'>SRC_URI_OVERRIDES_PACKAGE_ARCH</link></glossterm>
225 is in base.bbclass.
226 </para>
227 </answer>
228 </qandaentry>
229</qandaset>
230</appendix>
231<!--
232vim: expandtab tw=80 ts=4
233-->
234
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2026-08-06 22:11:27 +0000