summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/faq.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/poky-ref-manual/faq.xml')
-rw-r--r--documentation/poky-ref-manual/faq.xml96
1 files changed, 96 insertions, 0 deletions
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml
index 366db6c412..f4b5ae0fd1 100644
--- a/documentation/poky-ref-manual/faq.xml
+++ b/documentation/poky-ref-manual/faq.xml
@@ -413,6 +413,102 @@
413 </answer> 413 </answer>
414 </qandaentry> 414 </qandaentry>
415 415
416 <qandaentry>
417 <question>
418 <para>
419 How does Poky obtain source code and will it work behind my firewall or proxy server?
420 </para>
421 </question>
422 <answer>
423 <para>
424 The way Poky obtains source code is highly configurable.
425 You can setup Poky to get source code in most environmnents if
426 HTTP transport is available.
427 </para>
428 <para>
429 When Poky searches for source code it first tries the local download directory.
430 If that location fails, Poky tries PREMIRRORS, the upstream source,
431 and then MIRRORS in that order.
432 </para>
433 <para>
434 By default, Poky uses the Yocto Project source PREMIRRORS for SCM-based sources,
435 upstreams for normal tarballs and then falls back to a number of other mirrors
436 including the Yocto Project source mirror if those fail.
437 </para>
438 <para>
439 As an example, you could add a specific server for Poky to attempt before any
440 others by adding something like the following to the <filename>local.conf</filename>
441 configuration file:
442 <literallayout class='monospaced'>
443 PREMIRRORS_prepend = "\
444 git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
445 ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
446 http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
447 https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
448 </literallayout>
449 </para>
450 <para>
451 These changes cause Poky to intercept GIT, FTP, HTTP, and HTTPS
452 requests and direct them to the <filename>http://</filename> sources mirror.
453 You can use <filename>file://</filename> urls to point to local directories
454 or network shares as well.
455 </para>
456 <para>
457 Aside from the previous technique, these options also exist:
458 <literallayout class='monospaced'>
459 BB_NO_NETWORK = "1"
460 </literallayout>
461 </para>
462 <para>
463 This statement tells BitBake to throw an error instead of trying to access the
464 Internet.
465 This technique is useful if you want to ensure code builds only from local sources.
466 </para>
467 <para>
468 Here is another technique:
469 <literallayout class='monospaced'>
470 BB_FETCH_PREMIRRORONLY = "1"
471 </literallayout>
472 </para>
473 <para>
474 This statement limits Poky to pulling source from the PREMIRRORS only.
475 Again, this technique is useful for reproducing builds.
476 </para>
477 <para>
478 Here is another technique:
479 <literallayout class='monospaced'>
480 BB_GENERATE_MIRROR_TARBALLS = "1"
481 </literallayout>
482 </para>
483 <para>
484 This statement tells Poky to generate mirror tarballs.
485 This technique is useful if you want to create a mirror server.
486 If not, however, the technique can simply waste time during the build.
487 </para>
488 <para>
489 Finally, consider an example where you are behind an HTTP-only firewall.
490 You could make the following changes to the <filename>local.conf</filename>
491 configuration file as long as the premirror server is up to date:
492 <literallayout class='monospaced'>
493 PREMIRRORS_prepend = "\
494 ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
495 http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
496 https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
497 BB_FETCH_PREMIRRORONLY = "1"
498 </literallayout>
499 </para>
500 <para>
501 These changes would cause Poky to successfully fetch source over HTTP and
502 any network accesses to anything other than the premirror would fail.
503 </para>
504 <para>
505 Poky also honors the standard environment variables
506 <filename>http_proxy</filename>, <filename>ftp_proxy</filename>,
507 <filename>https_proxy</filename>, and <filename>all_proxy</filename>
508 to redirect requests through proxy servers.
509 </para>
510 </answer>
511 </qandaentry>
416 512
417 513
418 514