summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/start.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/start.rst')
-rw-r--r--documentation/dev-manual/start.rst18
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst
index 73548132a3..44bd2de137 100644
--- a/documentation/dev-manual/start.rst
+++ b/documentation/dev-manual/start.rst
@@ -109,7 +109,7 @@ particular working environment and set of practices.
109 109
110 - Keep your cross-development toolchains updated. You can do this 110 - Keep your cross-development toolchains updated. You can do this
111 through provisioning either as new toolchain downloads or as 111 through provisioning either as new toolchain downloads or as
112 updates through a package update mechanism using ``opkg`` to 112 updates through a package update mechanism to
113 provide updates to an existing toolchain. The exact mechanics of 113 provide updates to an existing toolchain. The exact mechanics of
114 how and when to do this depend on local policy. 114 how and when to do this depend on local policy.
115 115
@@ -159,7 +159,7 @@ particular working environment and set of practices.
159 are made. 159 are made.
160 160
161 - Allows triggering of automated image booting and testing under 161 - Allows triggering of automated image booting and testing under
162 the QuickEMUlator (QEMU). 162 the Quick EMUlator (QEMU).
163 163
164 - Supports incremental build testing and from-scratch builds. 164 - Supports incremental build testing and from-scratch builds.
165 165
@@ -234,7 +234,7 @@ particular working environment and set of practices.
234 - The Yocto Project community encourages you to send patches to the 234 - The Yocto Project community encourages you to send patches to the
235 project to fix bugs or add features. If you do submit patches, 235 project to fix bugs or add features. If you do submit patches,
236 follow the project commit guidelines for writing good commit 236 follow the project commit guidelines for writing good commit
237 messages. See the ":doc:`../contributor-guide/submit-changes`" 237 messages. See the ":doc:`/contributor-guide/submit-changes`"
238 section in the Yocto Project and OpenEmbedded Contributor Guide. 238 section in the Yocto Project and OpenEmbedded Contributor Guide.
239 239
240 - Send changes to the core sooner than later as others are likely 240 - Send changes to the core sooner than later as others are likely
@@ -310,7 +310,7 @@ Project Build Host:
310 310
311 - GNU make &MIN_MAKE_VERSION; or greater 311 - GNU make &MIN_MAKE_VERSION; or greater
312 312
313 If your build host does not meet any of these listed version 313 If your build host does not satisfy all of these listed version
314 requirements, you can take steps to prepare the system so that you 314 requirements, you can take steps to prepare the system so that you
315 can still use the Yocto Project. See the 315 can still use the Yocto Project. See the
316 ":ref:`ref-manual/system-requirements:required git, tar, python, make and gcc versions`" 316 ":ref:`ref-manual/system-requirements:required git, tar, python, make and gcc versions`"
@@ -568,7 +568,7 @@ extension accordingly.
568Locating Yocto Project Source Files 568Locating Yocto Project Source Files
569=================================== 569===================================
570 570
571This section shows you how to locate, fetch and configure the source 571This section shows you how to locate, fetch, unpack, patch and configure the source
572files you'll need to work with the Yocto Project. 572files you'll need to work with the Yocto Project.
573 573
574.. note:: 574.. note::
@@ -720,11 +720,11 @@ Follow these steps to create a local version of the upstream
720 $ git branch 720 $ git branch
721 * master 721 * master
722 722
723 Your local repository of poky is identical to the 723 Your local repository of poky is initially identical to the
724 upstream poky repository at the time from which it was cloned. As you 724 upstream poky repository from which it was cloned. As you
725 work with the local branch, you can periodically use the 725 work with the local branch, you can periodically use the
726 ``git pull --rebase`` command to be sure you are up-to-date 726 ``git pull`` command to be sure you stay up-to-date
727 with the upstream branch. 727 with the upstream poky branch.
728 728
729Checking Out by Branch in Poky 729Checking Out by Branch in Poky
730------------------------------ 730------------------------------