From ca77f37bf8e77087cedd19e4593aaf6fcef7fe81 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 19 Jun 2014 08:38:51 +0300 Subject: bitbake: bitbake-user-manual-intro.xml: Edits to "Obtaining BitBake" Updated the last bullet item that describes a final way to obtain a copy of BitBake. The example was too specific regarding Poky and OE. So, I made it quite generic and kept with the convention of not having any specific links from the BitBake manual into YP docs or such. (Bitbake rev: a2a3b534871aa23a5d442b93dd9660d5f9e27536) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml index 330bfbd3c3..41b9410e47 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml @@ -418,20 +418,19 @@ you have a directory entitled bitbake-1.17.0. - Using the BitBake that comes with your - build checkout: + Using the BitBake that Comes With Your + Build Checkout: A final possibility for getting a copy of BitBake is that it already comes with your checkout of a larger Bitbake-based build system, such as Poky or Yocto Project. Rather than manually checking out individual layers and gluing them together yourself, you can check - out an entire build system such as Poky with something like: - - $ git clone git://git.yoctoproject.org/poky - + out an entire build system. The checkout will already include a version of BitBake that has been thoroughly tested for compatibility with the other components. + For information on how to check out a particular BitBake-based + build system, the build system's supporting documentation. -- cgit v1.2.3-54-g00ecf