diff options
Diffstat (limited to 'poky/documentation/brief-yoctoprojectqs')
| -rw-r--r-- | poky/documentation/brief-yoctoprojectqs/index.rst | 73 |
1 files changed, 44 insertions, 29 deletions
diff --git a/poky/documentation/brief-yoctoprojectqs/index.rst b/poky/documentation/brief-yoctoprojectqs/index.rst index 4ac222c7e..974ae5ebc 100644 --- a/poky/documentation/brief-yoctoprojectqs/index.rst +++ b/poky/documentation/brief-yoctoprojectqs/index.rst @@ -60,10 +60,10 @@ following requirements: - - - Git 1.8.3.1 or greater - - tar 1.28 or greater - - Python 3.5.0 or greater. - - gcc 5.0 or greater. + - Git &MIN_GIT_VERSION; or greater + - tar &MIN_TAR_VERSION; or greater + - Python &MIN_PYTHON_VERSION; or greater. + - gcc &MIN_GCC_VERSION; or greater. If your build host does not meet any of these three listed version requirements, you can take steps to prepare the system so that you @@ -106,42 +106,57 @@ commands to clone the Poky repository. Resolving deltas: 100% (323116/323116), done. Checking connectivity... done. -Move to the ``poky`` directory and take a look at the tags: +Go to :yocto_wiki:`Releases wiki page </Releases>`, and choose a release +codename (such as ``&DISTRO_NAME_NO_CAP;``), corresponding to either the +latest stable release or a Long Term Support release. + +Then move to the ``poky`` directory and take a look at existing branches: .. code-block:: shell $ cd poky - $ git fetch --tags - $ git tag - 1.1_M1.final - 1.1_M1.rc1 - 1.1_M1.rc2 - 1.1_M2.final - 1.1_M2.rc1 + $ git branch -a + . + . + . + remotes/origin/HEAD -> origin/master + remotes/origin/dunfell + remotes/origin/dunfell-next + . + . + . + remotes/origin/gatesgarth + remotes/origin/gatesgarth-next + . . . + remotes/origin/master + remotes/origin/master-next . - yocto-2.5 - yocto-2.5.1 - yocto-2.5.2 - yocto-2.6 - yocto-2.6.1 - yocto-2.6.2 - yocto-2.7 - yocto_1.5_M5.rc8 - -For this example, check out the branch based on the -``&DISTRO_REL_TAG;`` release: + . + . + + +For this example, check out the ``&DISTRO_NAME_NO_CAP;`` branch based on the +``&DISTRO_NAME;`` release: .. code-block:: shell - $ git checkout tags/&DISTRO_REL_TAG; -b my-&DISTRO_REL_TAG; - Switched to a new branch 'my-&DISTRO_REL_TAG;' + $ git checkout -t origin/&DISTRO_NAME_NO_CAP; -b my-&DISTRO_NAME_NO_CAP; + Branch 'my-&DISTRO_NAME_NO_CAP;' set up to track remote branch '&DISTRO_NAME_NO_CAP;' from 'origin'. + Switched to a new branch 'my-&DISTRO_NAME_NO_CAP;' The previous Git checkout command creates a local branch named -``my-&DISTRO_REL_TAG;``. The files available to you in that branch exactly -match the repository's files in the ``&DISTRO_NAME_NO_CAP;`` development -branch at the time of the Yocto Project &DISTRO_REL_TAG; release. +``my-&DISTRO_NAME_NO_CAP;``. The files available to you in that branch +exactly match the repository's files in the ``&DISTRO_NAME_NO_CAP;`` +release branch. + +Note that you can regularly type the following command in the same directory +to keep your local files in sync with the release branch: + +.. code-block:: shell + + $ git pull For more options and information about accessing Yocto Project related repositories, see the @@ -204,7 +219,7 @@ an entire Linux distribution, including the toolchain, from source. meta-toolchain meta-ide-support - You can also run generated qemu images with a command like 'runqemu qemux86-64' + You can also run generated QEMU images with a command like 'runqemu qemux86-64' Among other things, the script creates the :term:`Build Directory`, which is ``build`` in this case and is located in the :term:`Source Directory`. After |