summaryrefslogtreecommitdiffstats
path: root/handbook
diff options
context:
space:
mode:
Diffstat (limited to 'handbook')
-rw-r--r--handbook/extendpoky.xml10
-rw-r--r--handbook/faq.xml2
-rw-r--r--handbook/introduction.xml3
-rw-r--r--handbook/usingpoky.xml14
4 files changed, 15 insertions, 14 deletions
diff --git a/handbook/extendpoky.xml b/handbook/extendpoky.xml
index cc0dc1fd25..f259d2ef0a 100644
--- a/handbook/extendpoky.xml
+++ b/handbook/extendpoky.xml
@@ -215,7 +215,7 @@ pkg_postinst_PACKAGENAME () {
215 <para> 215 <para>
216 Sometimes it is necessary that the execution of a post-installation 216 Sometimes it is necessary that the execution of a post-installation
217 script is delayed until the first boot, because the script 217 script is delayed until the first boot, because the script
218 needs to be executed the device itself. To delay script execution 218 needs to be executed on the device itself. To delay script execution
219 until boot time, the post-installation function should have the 219 until boot time, the post-installation function should have the
220 following structure: 220 following structure:
221 </para> 221 </para>
@@ -268,7 +268,7 @@ inherit poky-image
268 268
269 <para> 269 <para>
270 By creating a custom image, a developer has total control 270 By creating a custom image, a developer has total control
271 over the contents of the image. It is important use 271 over the contents of the image. It is important to use
272 the correct names of packages in the <glossterm><link 272 the correct names of packages in the <glossterm><link
273 linkend='var-IMAGE_INSTALL'>IMAGE_INSTALL</link></glossterm> variable. 273 linkend='var-IMAGE_INSTALL'>IMAGE_INSTALL</link></glossterm> variable.
274 The names must be in 274 The names must be in
@@ -295,11 +295,11 @@ IMAGE_INSTALL += "strace"
295 <title>Customising Images through custom tasks</title> 295 <title>Customising Images through custom tasks</title>
296 296
297 <para> 297 <para>
298 For for complex custom images, the best approach is to create a custom 298 For complex custom images, the best approach is to create a custom
299 task package which is them used to build the image (or images). A good 299 task package which is then used to build the image (or images). A good
300 example of a tasks package is <filename>meta/packages/tasks/task-poky.bb 300 example of a tasks package is <filename>meta/packages/tasks/task-poky.bb
301 </filename>. The <glossterm><link linkend='var-PACKAGES'>PACKAGES</link></glossterm> 301 </filename>. The <glossterm><link linkend='var-PACKAGES'>PACKAGES</link></glossterm>
302 variable lists the task packages to build (along with the complimentary 302 variable lists the task packages to build (along with the complementary
303 -dbg and -dev packages). For each package added, 303 -dbg and -dev packages). For each package added,
304 <glossterm><link linkend='var-PACKAGES'>RDEPENDS</link></glossterm> and 304 <glossterm><link linkend='var-PACKAGES'>RDEPENDS</link></glossterm> and
305 <glossterm><link linkend='var-PACKAGES'>RRECOMMENDS</link></glossterm> 305 <glossterm><link linkend='var-PACKAGES'>RRECOMMENDS</link></glossterm>
diff --git a/handbook/faq.xml b/handbook/faq.xml
index 7f5c4a962d..518069ed2a 100644
--- a/handbook/faq.xml
+++ b/handbook/faq.xml
@@ -253,7 +253,7 @@
253 In Intrepid, Ubuntu turned on by default normally optional compile-time security features 253 In Intrepid, Ubuntu turned on by default normally optional compile-time security features
254 and warnings. There are more details at <ulink 254 and warnings. There are more details at <ulink
255 url='https://wiki.ubuntu.com/CompilerFlags'>https://wiki.ubuntu.com/CompilerFlags</ulink>. 255 url='https://wiki.ubuntu.com/CompilerFlags'>https://wiki.ubuntu.com/CompilerFlags</ulink>.
256 You can work around this problem by disbaling those options by adding " -Wno-format-security -U_FORTIFY_SOURCE" 256 You can work around this problem by disabling those options by adding " -Wno-format-security -U_FORTIFY_SOURCE"
257 to the BUILD_CPPFLAGS variable in conf/bitbake.conf. 257 to the BUILD_CPPFLAGS variable in conf/bitbake.conf.
258 </para> 258 </para>
259 </answer> 259 </answer>
diff --git a/handbook/introduction.xml b/handbook/introduction.xml
index 7697bcd0cc..fd26b81097 100644
--- a/handbook/introduction.xml
+++ b/handbook/introduction.xml
@@ -69,7 +69,8 @@
69 69
70 <para> 70 <para>
71 71
72 Poky has a growing open source community backed up by commercial support provided by the principle developer and maintainer of Poky, <ulink url="http://o-hand.com/">OpenedHand Ltd</ulink>. 72 Poky has a growing open source community backed up by commercial support
73provided by the principal developer and maintainer of Poky, <ulink url="http://o-hand.com/">OpenedHand Ltd</ulink>.
73 74
74 </para> 75 </para>
75</section> 76</section>
diff --git a/handbook/usingpoky.xml b/handbook/usingpoky.xml
index c30da0716d..d54765c786 100644
--- a/handbook/usingpoky.xml
+++ b/handbook/usingpoky.xml
@@ -75,7 +75,7 @@
75 </para> 75 </para>
76 76
77 <para> 77 <para>
78 'package' can also used to describe recipes but since the same 78 'package' can also be used to describe recipes but since the same
79 word is used for the packaged output from Poky (i.e. .ipk or .deb 79 word is used for the packaged output from Poky (i.e. .ipk or .deb
80 files), this document will avoid it. 80 files), this document will avoid it.
81 </para> 81 </para>
@@ -114,7 +114,7 @@
114 <title>Running a Build</title> 114 <title>Running a Build</title>
115 115
116 <para> 116 <para>
117 First the Poky build environment needs to be setup using the following command: 117 First the Poky build environment needs to be set up using the following command:
118 </para> 118 </para>
119 <para> 119 <para>
120 <literallayout class='monospaced'> 120 <literallayout class='monospaced'>
@@ -122,7 +122,7 @@ $ source poky-init-build-env
122</literallayout> 122</literallayout>
123 </para> 123 </para>
124 <para> 124 <para>
125 Once the Poky build environment is setup, a target can now be built using: 125 Once the Poky build environment is set up, a target can now be built using:
126 </para> 126 </para>
127 <para> 127 <para>
128 <literallayout class='monospaced'> 128 <literallayout class='monospaced'>
@@ -204,11 +204,11 @@ route add default gw 192.168.7.200 tap0
204 <para> 204 <para>
205 The second is to configure name resolution which is configured in the 205 The second is to configure name resolution which is configured in the
206 <filename>/etc/resolv.conf</filename> file. The simplest solution is 206 <filename>/etc/resolv.conf</filename> file. The simplest solution is
207 to copy it's content from the host machine. 207 to copy its content from the host machine.
208 </para> 208 </para>
209 209
210 <para> 210 <para>
211 USB connections to devices can be setup and automated in a similar way. 211 USB connections to devices can be set up and automated in a similar way.
212 First add the following to 212 First add the following to
213 <filename>/etc/network/interfaces</filename>: 213 <filename>/etc/network/interfaces</filename>:
214 </para> 214 </para>
@@ -246,7 +246,7 @@ route add default gw 192.168.0.202 usb0
246 debugging practises such as comparing to the last 246 debugging practises such as comparing to the last
247 known working version and examining the changes, reapplying the 247 known working version and examining the changes, reapplying the
248 changes in steps to identify the one causing the problem etc. are 248 changes in steps to identify the one causing the problem etc. are
249 valid for Poky just like any other system. Its impossible to detail 249 valid for Poky just like any other system. It's impossible to detail
250 every possible potential failure here but there are some general 250 every possible potential failure here but there are some general
251 tips to aid debugging: 251 tips to aid debugging:
252 </para> 252 </para>
@@ -293,7 +293,7 @@ route add default gw 192.168.0.202 usb0
293 <para> 293 <para>
294 which would build matchbox-desktop, then recompile it. The 294 which would build matchbox-desktop, then recompile it. The
295 final command reruns all tasks after the compile (basically 295 final command reruns all tasks after the compile (basically
296 the packaging tasks) since bitbake will notice the the 296 the packaging tasks) since bitbake will notice that the
297 compile has been rerun and hence the other tasks also need 297 compile has been rerun and hence the other tasks also need
298 to run again. 298 to run again.
299 </para> 299 </para>