summaryrefslogtreecommitdiffstats
path: root/handbook/usingpoky.xml
diff options
context:
space:
mode:
Diffstat (limited to 'handbook/usingpoky.xml')
-rw-r--r--handbook/usingpoky.xml14
1 files changed, 7 insertions, 7 deletions
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>