summaryrefslogtreecommitdiffstats
path: root/documentation/yocto-project-qs
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2017-10-17 08:34:27 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-10-30 15:55:07 +0000
commitff7aa3dd430363d8a7f3cea3aafceee68c2fa2ce (patch)
tree083f0a64983202931c53c7d4277ae906c82912dc /documentation/yocto-project-qs
parenta4f6e19e3734b101f74a7d89288b8adf0fa3a1ca (diff)
downloadpoky-ff7aa3dd430363d8a7f3cea3aafceee68c2fa2ce.tar.gz
yocto-project-qs: Minor edits for readability
(From yocto-docs rev: 089c6e1392e6376e1e73f3ded74c40c60bee1109) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/yocto-project-qs')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml66
1 files changed, 35 insertions, 31 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 20f9ee0b04..3d7c5650b9 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -427,9 +427,9 @@
427 If your build host is using a Poky container, you can 427 If your build host is using a Poky container, you can
428 use the same Git commands. 428 use the same Git commands.
429 </note> 429 </note>
430 The example clones the <filename>poky</filename> repository 430 The following example clones the <filename>poky</filename>
431 and then checks out the latest Yocto Project Release by tag 431 repository and then checks out the latest Yocto Project Release
432 (i.e. <filename>&DISTRO_REL_TAG;</filename>): 432 by tag (i.e. <filename>&DISTRO_REL_TAG;</filename>):
433 <literallayout class='monospaced'> 433 <literallayout class='monospaced'>
434 $ git clone git://git.yoctoproject.org/poky 434 $ git clone git://git.yoctoproject.org/poky
435 Cloning into 'poky'... 435 Cloning into 'poky'...
@@ -456,8 +456,10 @@
456 Rather than checking out the entire development branch 456 Rather than checking out the entire development branch
457 of a release (i.e. the tip), which could be continuously 457 of a release (i.e. the tip), which could be continuously
458 changing while you are doing your development, you would 458 changing while you are doing your development, you would
459 check out a branch based on a release tag. Doing so 459 check out a branch based on a release tag as shown in
460 provides you with an unchanging, stable set of files. 460 the previous example.
461 Doing so provides you with an unchanging, stable set of
462 files.
461 </note> 463 </note>
462 </para> 464 </para>
463 465
@@ -479,7 +481,8 @@
479 your images. 481 your images.
480 <note> 482 <note>
481 A graphical user interface to the Yocto Project is available 483 A graphical user interface to the Yocto Project is available
482 through Toaster. 484 through
485 <ulink url='&YOCTO_DOCS_REF_URL;#toaster-term'>Toaster</ulink>.
483 See the 486 See the
484 <ulink url='&YOCTO_DOCS_TOAST_URL;'>Toaster User Manual</ulink> 487 <ulink url='&YOCTO_DOCS_TOAST_URL;'>Toaster User Manual</ulink>
485 for more information. 488 for more information.
@@ -518,31 +521,32 @@
518 Use the following commands to build your image. 521 Use the following commands to build your image.
519 The OpenEmbedded build system creates an entire Linux 522 The OpenEmbedded build system creates an entire Linux
520 distribution, including the toolchain, from source. 523 distribution, including the toolchain, from source.
521 <note><title>Note about Network Proxies</title> 524 <note><title>Notes about Network Proxies</title>
522 <para> 525 <itemizedlist>
523 By default, the build process searches for source code 526 <listitem><para>
524 using a pre-determined order through a set of 527 By default, the build process searches for source
525 locations. 528 code using a pre-determined order through a set of
526 If you are working behind a firewall and your build 529 locations.
527 host is not set up for proxies, you could encounter 530 If you are working behind a firewall and your build
528 problems with the build process when fetching source 531 host is not set up for proxies, you could encounter
529 code (e.g. fetcher failures or Git failures). 532 problems with the build process when fetching source
530 </para> 533 code (e.g. fetcher failures or Git failures).
531 534 </para></listitem>
532 <para> 535 <listitem><para>
533 If you do not know your proxy settings, consult your 536 If you do not know your proxy settings, consult your
534 local network infrastructure resources and get that 537 local network infrastructure resources and get that
535 information. 538 information.
536 A good starting point could also be to check your web 539 A good starting point could also be to check your
537 browser settings. 540 web browser settings.
538 Finally, you can find more information on using the 541 Finally, you can find more information on using the
539 Yocto Project behind a firewall in the Yocto Project 542 Yocto Project behind a firewall in the Yocto Project
540 Reference Manual 543 Reference Manual
541 <ulink url='&YOCTO_DOCS_REF_URL;#how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'>FAQ</ulink> 544 <ulink url='&YOCTO_DOCS_REF_URL;#how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'>FAQ</ulink>
542 and on the 545 and on the
543 "<ulink url='https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy'>Working Behind a Network Proxy</ulink>" 546 "<ulink url='https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy'>Working Behind a Network Proxy</ulink>"
544 wiki page. 547 wiki page.
545 </para> 548 </para></listitem>
549 </itemizedlist>
546 </note> 550 </note>
547 </para> 551 </para>
548 552