diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index a24eaa9473..bfc61e17c7 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml @@ -216,9 +216,9 @@ system in order to do any development using the Yocto Project. The name of the top-level directory of the Yocto Project file structure is derived from the Yocto Project release tarball. - For example, downloading and unpacking poky-edison-6.0.tar.bz2 + For example, downloading and unpacking poky-edison-6.0.1.tar.bz2 results in a Yocto Project file structure whose Yocto Project source directory is named - poky-edison-6.0. + poky-edison-6.0.1. If you create a Git repository, then you can name the repository anything you like. You can find instruction on how to set up the Yocto Project files on your host development system by reading @@ -233,9 +233,9 @@ You can create the Yocto Project build directory anywhere you want on your development system. Here is an example that creates the directory in mybuilds - and names the Yocto Project build directory YP-6.0: + and names the Yocto Project build directory YP-6.0.1: - $ source poky-edison-6.0/oe-init-build-env $HOME/mybuilds/YP-6.0 + $ source poky-edison-6.0.1/oe-init-build-env $HOME/mybuilds/YP-6.0.1 If you don't specifically name the directory, BitBake creates it in the current directory and uses the name build. diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 2535bc35a9..a9f1703719 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -79,7 +79,7 @@ into the current working directory and sets up the Yocto Project file structure with a top-level directory named poky-1.1.1: - $ tar xfj poky-edison-6.0.tar.bz2 + $ tar xfj poky-edison-6.0.1.tar.bz2 This method does not produce a Git repository. Instead, you simply end up with a local snapshot of the