From 1d60050201b792c4536cd94e0c9a04fd122eb0d4 Mon Sep 17 00:00:00 2001 From: Kristi Rifenbark Date: Thu, 29 Jun 2017 16:17:57 -0700 Subject: yocto-project-qs: Updated poky and meta-intel examples. Fixes [YOCTO #11731] Updated examples to so they checkout by tag rather than by branch name. (From yocto-docs rev: 9dca9fdc315998612f4cd5c9c69e2b3e045562ad) Signed-off-by: Kristi Rifenbark Signed-off-by: Richard Purdie --- .../yocto-project-qs/yocto-project-qs.xml | 56 ++++++++++++++++------ 1 file changed, 42 insertions(+), 14 deletions(-) (limited to 'documentation') diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index 58e8a30766..78881d4185 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -403,7 +403,8 @@ Here is an example from an Ubuntu build host that clones the poky repository and then checks out the - latest Yocto Project Release (i.e. &DISTRO;): + latest Yocto Project Release by tag + (i.e. &DISTRO_REL_TAG;): $ git clone git://git.yoctoproject.org/poky Cloning into 'poky'... @@ -413,17 +414,32 @@ Receiving objects: 100% (361782/361782), 131.94 MiB | 6.88 MiB/s, done. Resolving deltas: 100% (268619/268619), done. Checking connectivity... done. - $ git checkout &DISTRO_NAME_NO_CAP; + $ git checkout tags/&DISTRO_REL_TAG; -b poky_&DISTRO; - You can also get the Yocto Project Files by downloading - Yocto Project releases from the - Yocto Project website. - For more information on getting set up with the Yocto Project - release, see the - "Cloning the poky Repository" + The previous Git checkout command + creates a local branch named + poky_&DISTRO;. + 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; + release. + + Rather than checking out the entire development branch + of a release (i.e. the tip), which could be continuously + changing while you are doing your development, you would + check out a branch based on a release tag. Doing so + provides you with an unchanging, stable set of files. + + + + + For more options and information about accessing Yocto + Project related repositories, see the + "Working With Yocto Project Source Files" section in the Yocto Project Development Manual. @@ -737,15 +753,27 @@ sure that both repositories (meta-intel and poky) are using the same releases. - Consequently, you need to checkout out the - "&DISTRO_NAME_NO_CAP;" release after - cloning meta-intel: + Because you used the &DISTRO_REL_TAG; + tag when you checked out the poky + repository by tag, you should use a + meta-intel + tag that corresponds with the release you used for + poky. Consequently, you need to + checkout out the + "&METAINTELVERSION;-tbd-&YOCTO_DOC_VERSION;" + branch after cloning meta-intel: $ cd $HOME/poky/meta-intel - $ git checkout &DISTRO_NAME_NO_CAP; - Branch &DISTRO_NAME_NO_CAP; set up to track remote branch &DISTRO_NAME_NO_CAP; from origin. - Switched to a new branch '&DISTRO_NAME_NO_CAP;' + $ git checkout tags/&METAINTELVERSION;-tbd-&YOCTO_DOC_VERSION; -b meta-intel-&DISTRO_NAME_NO_CAP;-&YOCTO_DOC_VERSION; + Switched to a new branch 'meta-intel-&DISTRO_NAME_NO_CAP;-&YOCTO_DOC_VERSION;' + The previous Git checkout command + creates a local branch named + meta-intel-&DISTRO_NAME_NO_CAP;-&YOCTO_DOC_VERSION;. + You have the option to name your local branch whatever + you want by providing any name you like for + "meta-intel-&DISTRO_NAME_NO_CAP;-&YOCTO_DOC_VERSION;" + in the above example. Configure the Build: To configure the build, you edit the -- cgit v1.2.3-54-g00ecf