diff options
Diffstat (limited to 'documentation/poky-ref-manual/faq.xml')
-rw-r--r-- | documentation/poky-ref-manual/faq.xml | 181 |
1 files changed, 90 insertions, 91 deletions
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml index 945c7f19af..176573de28 100644 --- a/documentation/poky-ref-manual/faq.xml +++ b/documentation/poky-ref-manual/faq.xml | |||
@@ -19,11 +19,11 @@ | |||
19 | and BitBake. | 19 | and BitBake. |
20 | Thus, the generic term used here for the build system is | 20 | Thus, the generic term used here for the build system is |
21 | the "OpenEmbedded build system." | 21 | the "OpenEmbedded build system." |
22 | Development in the Yocto Project using Poky is closely tied to OpenEmbedded, with | 22 | Development in the Yocto Project using Poky is closely tied to OpenEmbedded, with |
23 | changes always being merged to OE-Core or BitBake first before being pulled back | 23 | changes always being merged to OE-Core or BitBake first before being pulled back |
24 | into Poky. | 24 | into Poky. |
25 | This practice benefits both projects immediately. | 25 | This practice benefits both projects immediately. |
26 | For a fuller description of the term "Poky", see the | 26 | For a fuller description of the term "Poky", see the |
27 | <ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> term in the Yocto Project | 27 | <ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> term in the Yocto Project |
28 | Development Manual. | 28 | Development Manual. |
29 | </para> | 29 | </para> |
@@ -47,9 +47,9 @@ | |||
47 | </itemizedlist> | 47 | </itemizedlist> |
48 | </para> | 48 | </para> |
49 | <para> | 49 | <para> |
50 | These tarballs are self-contained with all required libraries and should work | 50 | These tarballs are self-contained with all required libraries and should work |
51 | on most Linux systems. | 51 | on most Linux systems. |
52 | To use the tarballs extract them into the root | 52 | To use the tarballs extract them into the root |
53 | directory and run the appropriate command: | 53 | directory and run the appropriate command: |
54 | <literallayout class='monospaced'> | 54 | <literallayout class='monospaced'> |
55 | $ export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/:$PATH | 55 | $ export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/:$PATH |
@@ -72,12 +72,12 @@ | |||
72 | <para> | 72 | <para> |
73 | There are three areas that help with stability; | 73 | There are three areas that help with stability; |
74 | <itemizedlist> | 74 | <itemizedlist> |
75 | <listitem><para>The Yocto Project team keeps | 75 | <listitem><para>The Yocto Project team keeps |
76 | <ulink url='&YOCTO_DOCS_DEV_URL;#oe-core'>OE-Core</ulink> small | 76 | <ulink url='&YOCTO_DOCS_DEV_URL;#oe-core'>OE-Core</ulink> small |
77 | and focused, containing around 830 recipes as opposed to the thousands | 77 | and focused, containing around 830 recipes as opposed to the thousands |
78 | available in other OpenEmbedded community layers. | 78 | available in other OpenEmbedded community layers. |
79 | Keeping it small makes it easy to test and maintain.</para></listitem> | 79 | Keeping it small makes it easy to test and maintain.</para></listitem> |
80 | <listitem><para>The Yocto Project team runs manual and automated tests | 80 | <listitem><para>The Yocto Project team runs manual and automated tests |
81 | using a small, fixed set of reference hardware as well as emulated | 81 | using a small, fixed set of reference hardware as well as emulated |
82 | targets.</para></listitem> | 82 | targets.</para></listitem> |
83 | <listitem><para>The Yocto Project uses an an autobuilder, | 83 | <listitem><para>The Yocto Project uses an an autobuilder, |
@@ -100,7 +100,7 @@ | |||
100 | <ulink url='&YOCTO_DOCS_BSP_URL;'>Yocto Project Board Support Package (BSP) Developer's Guide</ulink>. | 100 | <ulink url='&YOCTO_DOCS_BSP_URL;'>Yocto Project Board Support Package (BSP) Developer's Guide</ulink>. |
101 | </para> | 101 | </para> |
102 | <para> | 102 | <para> |
103 | Usually, if the board is not completely exotic, adding support in | 103 | Usually, if the board is not completely exotic, adding support in |
104 | the Yocto Project is fairly straightforward. | 104 | the Yocto Project is fairly straightforward. |
105 | </para> | 105 | </para> |
106 | </answer> | 106 | </answer> |
@@ -115,10 +115,10 @@ | |||
115 | <answer> | 115 | <answer> |
116 | <para> | 116 | <para> |
117 | The software running on the <ulink url='http://vernier.com/labquest/'>Vernier LabQuest</ulink> | 117 | The software running on the <ulink url='http://vernier.com/labquest/'>Vernier LabQuest</ulink> |
118 | is built using the OpenEmbedded build system. | 118 | is built using the OpenEmbedded build system. |
119 | See the <ulink url='http://www.vernier.com/products/interfaces/labq/'>Vernier LabQuest</ulink> | 119 | See the <ulink url='http://www.vernier.com/products/interfaces/labq/'>Vernier LabQuest</ulink> |
120 | website for more information. | 120 | website for more information. |
121 | There are a number of pre-production devices using the OpenEmbedded build system | 121 | There are a number of pre-production devices using the OpenEmbedded build system |
122 | and the Yocto Project team | 122 | and the Yocto Project team |
123 | announces them as soon as they are released. | 123 | announces them as soon as they are released. |
124 | </para> | 124 | </para> |
@@ -133,8 +133,8 @@ | |||
133 | </question> | 133 | </question> |
134 | <answer> | 134 | <answer> |
135 | <para> | 135 | <para> |
136 | Because the same set of recipes can be used to create output of various formats, the | 136 | Because the same set of recipes can be used to create output of various formats, the |
137 | output of an OpenEmbedded build depends on how it was started. | 137 | output of an OpenEmbedded build depends on how it was started. |
138 | Usually, the output is a flashable image ready for the target device. | 138 | Usually, the output is a flashable image ready for the target device. |
139 | </para> | 139 | </para> |
140 | </answer> | 140 | </answer> |
@@ -150,7 +150,7 @@ | |||
150 | <para> | 150 | <para> |
151 | To add a package, you need to create a BitBake recipe. | 151 | To add a package, you need to create a BitBake recipe. |
152 | For information on how to add a package, see the section | 152 | For information on how to add a package, see the section |
153 | "<ulink url='&YOCTO_DOCS_DEV_URL;#usingpoky-extend-addpkg'>Adding a Package</ulink>" | 153 | "<ulink url='&YOCTO_DOCS_DEV_URL;#usingpoky-extend-addpkg'>Adding a Package</ulink>" |
154 | in the Yocto Project Development Manual. | 154 | in the Yocto Project Development Manual. |
155 | </para> | 155 | </para> |
156 | </answer> | 156 | </answer> |
@@ -159,16 +159,16 @@ | |||
159 | <qandaentry> | 159 | <qandaentry> |
160 | <question> | 160 | <question> |
161 | <para> | 161 | <para> |
162 | Do I have to reflash my entire board with a new Yocto Project image when recompiling | 162 | Do I have to reflash my entire board with a new Yocto Project image when recompiling |
163 | a package? | 163 | a package? |
164 | </para> | 164 | </para> |
165 | </question> | 165 | </question> |
166 | <answer> | 166 | <answer> |
167 | <para> | 167 | <para> |
168 | The OpenEmbedded build system can build packages in various formats such as | 168 | The OpenEmbedded build system can build packages in various formats such as |
169 | <filename>ipk</filename> for <filename>opkg</filename>, | 169 | <filename>ipk</filename> for <filename>opkg</filename>, |
170 | Debian package (<filename>.deb</filename>), or RPM. | 170 | Debian package (<filename>.deb</filename>), or RPM. |
171 | The packages can then be upgraded using the package tools on the device, much like | 171 | The packages can then be upgraded using the package tools on the device, much like |
172 | on a desktop distribution such as Ubuntu or Fedora. | 172 | on a desktop distribution such as Ubuntu or Fedora. |
173 | </para> | 173 | </para> |
174 | </answer> | 174 | </answer> |
@@ -182,11 +182,11 @@ | |||
182 | </question> | 182 | </question> |
183 | <answer> | 183 | <answer> |
184 | <para> | 184 | <para> |
185 | GNOME Mobile is a subset of the <ulink url='http://www.gnome.org'>GNOME</ulink> | 185 | GNOME Mobile is a subset of the <ulink url='http://www.gnome.org'>GNOME</ulink> |
186 | platform targeted at mobile and embedded devices. | 186 | platform targeted at mobile and embedded devices. |
187 | The the main difference between GNOME Mobile and standard GNOME is that | 187 | The the main difference between GNOME Mobile and standard GNOME is that |
188 | desktop-orientated libraries have been removed, along with deprecated libraries, | 188 | desktop-orientated libraries have been removed, along with deprecated libraries, |
189 | creating a much smaller footprint. | 189 | creating a much smaller footprint. |
190 | </para> | 190 | </para> |
191 | </answer> | 191 | </answer> |
192 | </qandaentry> | 192 | </qandaentry> |
@@ -200,7 +200,7 @@ | |||
200 | </question> | 200 | </question> |
201 | <answer> | 201 | <answer> |
202 | <para> | 202 | <para> |
203 | You are probably running the build on an NTFS filesystem. | 203 | You are probably running the build on an NTFS filesystem. |
204 | Use <filename>ext2</filename>, <filename>ext3</filename>, or <filename>ext4</filename> instead. | 204 | Use <filename>ext2</filename>, <filename>ext3</filename>, or <filename>ext4</filename> instead. |
205 | </para> | 205 | </para> |
206 | </answer> | 206 | </answer> |
@@ -214,8 +214,8 @@ | |||
214 | </question> | 214 | </question> |
215 | <answer> | 215 | <answer> |
216 | <para> | 216 | <para> |
217 | To get the Yocto Project working under RHEL/CentOS 5.1 you need to first | 217 | To get the Yocto Project working under RHEL/CentOS 5.1 you need to first |
218 | install some required packages. | 218 | install some required packages. |
219 | The standard CentOS packages needed are: | 219 | The standard CentOS packages needed are: |
220 | <itemizedlist> | 220 | <itemizedlist> |
221 | <listitem><para>"Development tools" (selected during installation)</para></listitem> | 221 | <listitem><para>"Development tools" (selected during installation)</para></listitem> |
@@ -224,19 +224,19 @@ | |||
224 | </itemizedlist> | 224 | </itemizedlist> |
225 | On top of these, you need the following external packages: | 225 | On top of these, you need the following external packages: |
226 | <itemizedlist> | 226 | <itemizedlist> |
227 | <listitem><para><filename>python-sqlite2</filename> from | 227 | <listitem><para><filename>python-sqlite2</filename> from |
228 | <ulink url='http://dag.wieers.com/rpm/packages/python-sqlite2/'>DAG repository</ulink> | 228 | <ulink url='http://dag.wieers.com/rpm/packages/python-sqlite2/'>DAG repository</ulink> |
229 | </para></listitem> | 229 | </para></listitem> |
230 | <listitem><para><filename>help2man</filename> from | 230 | <listitem><para><filename>help2man</filename> from |
231 | <ulink url='http://centos.karan.org/el4/extras/stable/x86_64/RPMS/repodata/repoview/help2man-0-1.33.1-2.html'>Karan repository</ulink></para></listitem> | 231 | <ulink url='http://centos.karan.org/el4/extras/stable/x86_64/RPMS/repodata/repoview/help2man-0-1.33.1-2.html'>Karan repository</ulink></para></listitem> |
232 | </itemizedlist> | 232 | </itemizedlist> |
233 | </para> | 233 | </para> |
234 | 234 | ||
235 | <para> | 235 | <para> |
236 | Once these packages are installed, the OpenEmbedded build system will be able | 236 | Once these packages are installed, the OpenEmbedded build system will be able |
237 | to build standard images. | 237 | to build standard images. |
238 | However, there might be a problem with the QEMU emulator segfaulting. | 238 | However, there might be a problem with the QEMU emulator segfaulting. |
239 | You can either disable the generation of binary locales by setting | 239 | You can either disable the generation of binary locales by setting |
240 | <filename><link linkend='var-ENABLE_BINARY_LOCALE_GENERATION'>ENABLE_BINARY_LOCALE_GENERATION</link> | 240 | <filename><link linkend='var-ENABLE_BINARY_LOCALE_GENERATION'>ENABLE_BINARY_LOCALE_GENERATION</link> |
241 | </filename> to "0" or by removing the <filename>linux-2.6-execshield.patch</filename> | 241 | </filename> to "0" or by removing the <filename>linux-2.6-execshield.patch</filename> |
242 | from the kernel and rebuilding it since that is the patch that causes the problems with QEMU. | 242 | from the kernel and rebuilding it since that is the patch that causes the problems with QEMU. |
@@ -247,22 +247,22 @@ | |||
247 | <qandaentry> | 247 | <qandaentry> |
248 | <question> | 248 | <question> |
249 | <para> | 249 | <para> |
250 | I see lots of 404 responses for files on | 250 | I see lots of 404 responses for files on |
251 | <filename>http://www.yoctoproject.org/sources/*</filename>. Is something wrong? | 251 | <filename>http://www.yoctoproject.org/sources/*</filename>. Is something wrong? |
252 | </para> | 252 | </para> |
253 | </question> | 253 | </question> |
254 | <answer> | 254 | <answer> |
255 | <para> | 255 | <para> |
256 | Nothing is wrong. | 256 | Nothing is wrong. |
257 | The OpenEmbedded build system checks any configured source mirrors before downloading | 257 | The OpenEmbedded build system checks any configured source mirrors before downloading |
258 | from the upstream sources. | 258 | from the upstream sources. |
259 | The build system does this searching for both source archives and | 259 | The build system does this searching for both source archives and |
260 | pre-checked out versions of SCM managed software. | 260 | pre-checked out versions of SCM managed software. |
261 | These checks help in large installations because it can reduce load on the SCM servers | 261 | These checks help in large installations because it can reduce load on the SCM servers |
262 | themselves. | 262 | themselves. |
263 | The address above is one of the default mirrors configured into the | 263 | The address above is one of the default mirrors configured into the |
264 | build system. | 264 | build system. |
265 | Consequently, if an upstream source disappears, the team | 265 | Consequently, if an upstream source disappears, the team |
266 | can place sources there so builds continue to work. | 266 | can place sources there so builds continue to work. |
267 | </para> | 267 | </para> |
268 | </answer> | 268 | </answer> |
@@ -271,16 +271,16 @@ | |||
271 | <qandaentry> | 271 | <qandaentry> |
272 | <question> | 272 | <question> |
273 | <para> | 273 | <para> |
274 | I have machine-specific data in a package for one machine only but the package is | 274 | I have machine-specific data in a package for one machine only but the package is |
275 | being marked as machine-specific in all cases, how do I prevent this? | 275 | being marked as machine-specific in all cases, how do I prevent this? |
276 | </para> | 276 | </para> |
277 | </question> | 277 | </question> |
278 | <answer> | 278 | <answer> |
279 | <para> | 279 | <para> |
280 | Set <filename><link linkend='var-SRC_URI_OVERRIDES_PACKAGE_ARCH'>SRC_URI_OVERRIDES_PACKAGE_ARCH</link> | 280 | Set <filename><link linkend='var-SRC_URI_OVERRIDES_PACKAGE_ARCH'>SRC_URI_OVERRIDES_PACKAGE_ARCH</link> |
281 | </filename> = "0" in the <filename>.bb</filename> file but make sure the package is | 281 | </filename> = "0" in the <filename>.bb</filename> file but make sure the package is |
282 | manually marked as | 282 | manually marked as |
283 | machine-specific in the case that needs it. | 283 | machine-specific in the case that needs it. |
284 | The code that handles <filename>SRC_URI_OVERRIDES_PACKAGE_ARCH</filename> is in <filename>base.bbclass</filename>. | 284 | The code that handles <filename>SRC_URI_OVERRIDES_PACKAGE_ARCH</filename> is in <filename>base.bbclass</filename>. |
285 | </para> | 285 | </para> |
286 | </answer> | 286 | </answer> |
@@ -295,9 +295,9 @@ | |||
295 | <answer> | 295 | <answer> |
296 | <para> | 296 | <para> |
297 | Most source fetching by the OpenEmbedded build system is done by <filename>wget</filename> | 297 | Most source fetching by the OpenEmbedded build system is done by <filename>wget</filename> |
298 | and you therefore need to specify the proxy settings in a | 298 | and you therefore need to specify the proxy settings in a |
299 | <filename>.wgetrc</filename> file in your home directory. | 299 | <filename>.wgetrc</filename> file in your home directory. |
300 | Example settings in that file would be | 300 | Example settings in that file would be |
301 | <literallayout class='monospaced'> | 301 | <literallayout class='monospaced'> |
302 | http_proxy = http://proxy.yoyodyne.com:18023/ | 302 | http_proxy = http://proxy.yoyodyne.com:18023/ |
303 | ftp_proxy = http://proxy.yoyodyne.com:18023/ | 303 | ftp_proxy = http://proxy.yoyodyne.com:18023/ |
@@ -317,10 +317,10 @@ | |||
317 | </question> | 317 | </question> |
318 | <answer> | 318 | <answer> |
319 | <para> | 319 | <para> |
320 | The <filename>*-native</filename> targets are designed to run on the system | 320 | The <filename>*-native</filename> targets are designed to run on the system |
321 | being used for the build. | 321 | being used for the build. |
322 | These are usually tools that are needed to assist the build in some way such as | 322 | These are usually tools that are needed to assist the build in some way such as |
323 | <filename>quilt-native</filename>, which is used to apply patches. | 323 | <filename>quilt-native</filename>, which is used to apply patches. |
324 | The non-native version is the one that runs on the target device. | 324 | The non-native version is the one that runs on the target device. |
325 | </para> | 325 | </para> |
326 | </answer> | 326 | </answer> |
@@ -335,11 +335,11 @@ | |||
335 | <answer> | 335 | <answer> |
336 | <para> | 336 | <para> |
337 | If the same build is failing in totally different and random ways, | 337 | If the same build is failing in totally different and random ways, |
338 | the most likely explanation is that either the hardware you're running the | 338 | the most likely explanation is that either the hardware you're running the |
339 | build on has some problem, or, if you are running the build under virtualisation, | 339 | build on has some problem, or, if you are running the build under virtualisation, |
340 | the virtualisation probably has bugs. | 340 | the virtualisation probably has bugs. |
341 | The OpenEmbedded build system processes a massive amount of data causing lots of network, disk and | 341 | The OpenEmbedded build system processes a massive amount of data causing lots of network, disk and |
342 | CPU activity and is sensitive to even single bit failures in any of these areas. | 342 | CPU activity and is sensitive to even single bit failures in any of these areas. |
343 | True random failures have always been traced back to hardware or virtualisation issues. | 343 | True random failures have always been traced back to hardware or virtualisation issues. |
344 | </para> | 344 | </para> |
345 | </answer> | 345 | </answer> |
@@ -356,8 +356,8 @@ | |||
356 | This is a difficult question and you need to consult your lawyer for the answer | 356 | This is a difficult question and you need to consult your lawyer for the answer |
357 | for your specific case. | 357 | for your specific case. |
358 | It is worth bearing in mind that for GPL compliance there needs to be enough | 358 | It is worth bearing in mind that for GPL compliance there needs to be enough |
359 | information shipped to allow someone else to rebuild the same end result | 359 | information shipped to allow someone else to rebuild the same end result |
360 | you are shipping. | 360 | you are shipping. |
361 | This means sharing the source code, any patches applied to it, and also any | 361 | This means sharing the source code, any patches applied to it, and also any |
362 | configuration information about how that package was configured and built. | 362 | configuration information about how that package was configured and built. |
363 | </para> | 363 | </para> |
@@ -390,9 +390,9 @@ | |||
390 | </question> | 390 | </question> |
391 | <answer> | 391 | <answer> |
392 | <para> | 392 | <para> |
393 | The default interfaces file provided by the netbase recipe does not | 393 | The default interfaces file provided by the netbase recipe does not |
394 | automatically bring up network interfaces. | 394 | automatically bring up network interfaces. |
395 | Therefore, you will need to add a BSP-specific netbase that includes an interfaces | 395 | Therefore, you will need to add a BSP-specific netbase that includes an interfaces |
396 | file. | 396 | file. |
397 | See the "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout-misc-recipes'>Miscellaneous Recipe Files</ulink>" | 397 | See the "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout-misc-recipes'>Miscellaneous Recipe Files</ulink>" |
398 | section for information on creating these types of miscellaneous recipe files. | 398 | section for information on creating these types of miscellaneous recipe files. |
@@ -415,11 +415,11 @@ | |||
415 | </question> | 415 | </question> |
416 | <answer> | 416 | <answer> |
417 | <para> | 417 | <para> |
418 | Images are created to be 1.2 times the size of the populated root filesystem. | 418 | Images are created to be 1.2 times the size of the populated root filesystem. |
419 | To modify this ratio so that there is more free space available, you need to | 419 | To modify this ratio so that there is more free space available, you need to |
420 | set the configuration value <filename>IMAGE_OVERHEAD_FACTOR</filename>. | 420 | set the configuration value <filename>IMAGE_OVERHEAD_FACTOR</filename>. |
421 | For example, setting <filename>IMAGE_OVERHEAD_FACTOR</filename> to 1.5 sets | 421 | For example, setting <filename>IMAGE_OVERHEAD_FACTOR</filename> to 1.5 sets |
422 | the image size ratio to one and a half times the size of the populated | 422 | the image size ratio to one and a half times the size of the populated |
423 | root filesystem. | 423 | root filesystem. |
424 | <literallayout class='monospaced'> | 424 | <literallayout class='monospaced'> |
425 | IMAGE_OVERHEAD_FACTOR = "1.5" | 425 | IMAGE_OVERHEAD_FACTOR = "1.5" |
@@ -436,9 +436,9 @@ | |||
436 | </question> | 436 | </question> |
437 | <answer> | 437 | <answer> |
438 | <para> | 438 | <para> |
439 | The Yocto Project team has tried to do this before but too many of the tools | 439 | The Yocto Project team has tried to do this before but too many of the tools |
440 | the OpenEmbedded build system depends on such as <filename>autoconf</filename> | 440 | the OpenEmbedded build system depends on such as <filename>autoconf</filename> |
441 | break when they find spaces in pathnames. | 441 | break when they find spaces in pathnames. |
442 | Until that situation changes, the team will not support spaces in pathnames. | 442 | Until that situation changes, the team will not support spaces in pathnames. |
443 | </para> | 443 | </para> |
444 | </answer> | 444 | </answer> |
@@ -453,10 +453,10 @@ | |||
453 | <answer> | 453 | <answer> |
454 | <para> | 454 | <para> |
455 | The toolchain configuration is very flexible and customizable. | 455 | The toolchain configuration is very flexible and customizable. |
456 | It is primarily controlled with the | 456 | It is primarily controlled with the |
457 | <filename><link linkend='var-TCMODE'>TCMODE</link></filename> variable. | 457 | <filename><link linkend='var-TCMODE'>TCMODE</link></filename> variable. |
458 | This variable controls which <filename>tcmode-*.inc</filename> file to include | 458 | This variable controls which <filename>tcmode-*.inc</filename> file to include |
459 | from the <filename>meta/conf/distro/include</filename> directory within the | 459 | from the <filename>meta/conf/distro/include</filename> directory within the |
460 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. | 460 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. |
461 | </para> | 461 | </para> |
462 | 462 | ||
@@ -466,15 +466,15 @@ | |||
466 | However, other patterns are accepted. | 466 | However, other patterns are accepted. |
467 | In particular, "external-*" refers to external toolchains of which there are some | 467 | In particular, "external-*" refers to external toolchains of which there are some |
468 | basic examples included in the OpenEmbedded Core (<filename>meta</filename>). | 468 | basic examples included in the OpenEmbedded Core (<filename>meta</filename>). |
469 | You can use your own custom toolchain definition in your own layer | 469 | You can use your own custom toolchain definition in your own layer |
470 | (or as defined in the <filename>local.conf</filename> file) at the location | 470 | (or as defined in the <filename>local.conf</filename> file) at the location |
471 | <filename>conf/distro/include/tcmode-*.inc</filename>. | 471 | <filename>conf/distro/include/tcmode-*.inc</filename>. |
472 | </para> | 472 | </para> |
473 | 473 | ||
474 | <para> | 474 | <para> |
475 | In addition to the toolchain configuration, you also need a corresponding toolchain recipe file. | 475 | In addition to the toolchain configuration, you also need a corresponding toolchain recipe file. |
476 | This recipe file needs to package up any pre-built objects in the toolchain such as | 476 | This recipe file needs to package up any pre-built objects in the toolchain such as |
477 | <filename>libgcc</filename>, <filename>libstdcc++</filename>, | 477 | <filename>libgcc</filename>, <filename>libstdcc++</filename>, |
478 | any locales, and <filename>libc</filename>. | 478 | any locales, and <filename>libc</filename>. |
479 | An example is the <filename>external-sourcery-toolchain.bb</filename>, which is located | 479 | An example is the <filename>external-sourcery-toolchain.bb</filename>, which is located |
480 | in <filename>meta/recipes-core/meta/</filename> within the source directory. | 480 | in <filename>meta/recipes-core/meta/</filename> within the source directory. |
@@ -485,7 +485,7 @@ | |||
485 | <qandaentry> | 485 | <qandaentry> |
486 | <question> | 486 | <question> |
487 | <para id='how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'> | 487 | <para id='how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'> |
488 | How does the OpenEmbedded build system obtain source code and will it work behind my | 488 | How does the OpenEmbedded build system obtain source code and will it work behind my |
489 | firewall or proxy server? | 489 | firewall or proxy server? |
490 | </para> | 490 | </para> |
491 | </question> | 491 | </question> |
@@ -497,13 +497,13 @@ | |||
497 | </para> | 497 | </para> |
498 | <para> | 498 | <para> |
499 | When the build system searches for source code, it first tries the local download directory. | 499 | When the build system searches for source code, it first tries the local download directory. |
500 | If that location fails, Poky tries PREMIRRORS, the upstream source, | 500 | If that location fails, Poky tries PREMIRRORS, the upstream source, |
501 | and then MIRRORS in that order. | 501 | and then MIRRORS in that order. |
502 | </para> | 502 | </para> |
503 | <para> | 503 | <para> |
504 | By default, the OpenEmbedded build system uses the Yocto Project source PREMIRRORS | 504 | By default, the OpenEmbedded build system uses the Yocto Project source PREMIRRORS |
505 | for SCM-based sources, | 505 | for SCM-based sources, |
506 | upstreams for normal tarballs, and then falls back to a number of other mirrors | 506 | upstreams for normal tarballs, and then falls back to a number of other mirrors |
507 | including the Yocto Project source mirror if those fail. | 507 | including the Yocto Project source mirror if those fail. |
508 | </para> | 508 | </para> |
509 | <para> | 509 | <para> |
@@ -521,7 +521,7 @@ | |||
521 | <para> | 521 | <para> |
522 | These changes cause Poky to intercept Git, FTP, HTTP, and HTTPS | 522 | These changes cause Poky to intercept Git, FTP, HTTP, and HTTPS |
523 | requests and direct them to the <filename>http://</filename> sources mirror. | 523 | requests and direct them to the <filename>http://</filename> sources mirror. |
524 | You can use <filename>file://</filename> URLs to point to local directories | 524 | You can use <filename>file://</filename> URLs to point to local directories |
525 | or network shares as well. | 525 | or network shares as well. |
526 | </para> | 526 | </para> |
527 | <para> | 527 | <para> |
@@ -529,7 +529,7 @@ | |||
529 | <literallayout class='monospaced'> | 529 | <literallayout class='monospaced'> |
530 | BB_NO_NETWORK = "1" | 530 | BB_NO_NETWORK = "1" |
531 | </literallayout> | 531 | </literallayout> |
532 | This statement tells BitBake to throw an error instead of trying to access the | 532 | This statement tells BitBake to throw an error instead of trying to access the |
533 | Internet. | 533 | Internet. |
534 | This technique is useful if you want to ensure code builds only from local sources. | 534 | This technique is useful if you want to ensure code builds only from local sources. |
535 | </para> | 535 | </para> |
@@ -559,14 +559,14 @@ | |||
559 | ftp://.*/.* http://www.yoctoproject.org/sources/ \n \ | 559 | ftp://.*/.* http://www.yoctoproject.org/sources/ \n \ |
560 | http://.*/.* http://www.yoctoproject.org/sources/ \n \ | 560 | http://.*/.* http://www.yoctoproject.org/sources/ \n \ |
561 | https://.*/.* http://www.yoctoproject.org/sources/ \n" | 561 | https://.*/.* http://www.yoctoproject.org/sources/ \n" |
562 | BB_FETCH_PREMIRRORONLY = "1" | 562 | BB_FETCH_PREMIRRORONLY = "1" |
563 | </literallayout> | 563 | </literallayout> |
564 | These changes would cause Poky to successfully fetch source over HTTP and | 564 | These changes would cause Poky to successfully fetch source over HTTP and |
565 | any network accesses to anything other than the PREMIRROR would fail. | 565 | any network accesses to anything other than the PREMIRROR would fail. |
566 | </para> | 566 | </para> |
567 | <para> | 567 | <para> |
568 | The build system also honors the standard shell environment variables | 568 | The build system also honors the standard shell environment variables |
569 | <filename>http_proxy</filename>, <filename>ftp_proxy</filename>, | 569 | <filename>http_proxy</filename>, <filename>ftp_proxy</filename>, |
570 | <filename>https_proxy</filename>, and <filename>all_proxy</filename> | 570 | <filename>https_proxy</filename>, and <filename>all_proxy</filename> |
571 | to redirect requests through proxy servers. | 571 | to redirect requests through proxy servers. |
572 | </para> | 572 | </para> |
@@ -582,16 +582,16 @@ | |||
582 | <answer> | 582 | <answer> |
583 | <para> | 583 | <para> |
584 | Yes - you can easily do this. | 584 | Yes - you can easily do this. |
585 | When you use BitBake to build an image, all the build output goes into the | 585 | When you use BitBake to build an image, all the build output goes into the |
586 | directory created when you source the <filename>oe-init-build-env</filename> | 586 | directory created when you source the <filename>oe-init-build-env</filename> |
587 | setup file. | 587 | setup file. |
588 | By default, this <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink> | 588 | By default, this <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink> |
589 | is named <filename>build</filename> but can be named | 589 | is named <filename>build</filename> but can be named |
590 | anything you want. | 590 | anything you want. |
591 | </para> | 591 | </para> |
592 | 592 | ||
593 | <para> | 593 | <para> |
594 | Within the build directory is the <filename>tmp</filename> directory. | 594 | Within the build directory is the <filename>tmp</filename> directory. |
595 | To remove all the build output yet preserve any source code or downloaded files | 595 | To remove all the build output yet preserve any source code or downloaded files |
596 | from previous builds, simply remove the <filename>tmp</filename> directory. | 596 | from previous builds, simply remove the <filename>tmp</filename> directory. |
597 | </para> | 597 | </para> |
@@ -601,7 +601,6 @@ | |||
601 | 601 | ||
602 | </qandaset> | 602 | </qandaset> |
603 | </chapter> | 603 | </chapter> |
604 | <!-- | 604 | <!-- |
605 | vim: expandtab tw=80 ts=4 | 605 | vim: expandtab tw=80 ts=4 |
606 | --> | 606 | --> |
607 | |||