From e3550b4f283b4cde4677bf6c2e0db8fa7f68184d Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 1 Jul 2013 08:22:24 +0300 Subject: dev-manual: Changed repo name. Changed the poky-extras repo name to meta-yocto-kernel-extras repo. This repository had become stale and Bruce did some work to freshen it up a bit. The name was poor too. That drove the name change. (From yocto-docs rev: 4fa2b0f86cfe7191b8de7577d8d8ad6adb984a4e) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-start.xml | 38 +++++++++++++-------------- 1 file changed, 19 insertions(+), 19 deletions(-) (limited to 'documentation/dev-manual/dev-manual-start.xml') diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 02f6bd0452..092039368c 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -72,10 +72,10 @@ Packages: The OpenEmbedded build system requires certain packages exist on your development system (e.g. Python 2.6 or 2.7). See "The Packages" - section in the Yocto Project Quick Start and the + section in the Yocto Project Quick Start and the "Required Packages for the Host Development System" - section in the Yocto Project Reference Manual for the exact - package requirements and the installation commands to install + section in the Yocto Project Reference Manual for the exact + package requirements and the installation commands to install them for the supported distributions. Yocto Project Release: @@ -88,14 +88,14 @@ hierarchical set of files as the "Source Directory." - Tarball Extraction: - If you are not going to contribute back into the Yocto - Project, you can simply go to the - Yocto Project Website, + Tarball Extraction: + If you are not going to contribute back into the Yocto + Project, you can simply go to the + Yocto Project Website, select the "Downloads" tab, and choose what you want. - Once you have the tarball, just extract it into a + Once you have the tarball, just extract it into a directory of your choice. - For example, the following command extracts the + For example, the following command extracts the Yocto Project &DISTRO; release tarball into the current working directory and sets up the local Source Directory with a top-level folder named &YOCTO_POKY;: @@ -126,7 +126,7 @@ remote: Compressing objects: 100% (47428/47428), done. remote: Total 183981 (delta 132271), reused 183703 (delta 132044) Receiving objects: 100% (183981/183981), 89.71 MiB | 2.93 MiB/s, done. - Resolving deltas: 100% (132271/132271), done. + Resolving deltas: 100% (132271/132271), done. For another example of how to set up your own local Git repositories, see this @@ -168,9 +168,9 @@ Cloning into 'my-linux-yocto-3.8-work'... done. - - The poky-extras Git Repository: - The poky-extras Git repository contains Metadata needed + + The meta-yocto-kernel-extras Git Repository: + The meta-yocto-kernel-extras Git repository contains Metadata needed only if you are modifying and building the kernel image. In particular, it contains the kernel BitBake append (.bbappend) files that you @@ -178,17 +178,17 @@ image. Pointing to these local files is much more efficient than requiring a download of the kernel's source files from upstream each time you make changes to the kernel. - You can find the poky-extras Git Repository in the + You can find the meta-yocto-kernel-extras Git Repository in the "Yocto Metadata Layers" area of the Yocto Project Source Repositories at . It is good practice to create this Git repository inside the Source Directory. - Following is an example that creates the poky-extras Git + Following is an example that creates the meta-yocto-kernel-extras Git repository inside the Source Directory, which is named poky in this case: $ cd ~/poky - $ git clone git://git.yoctoproject.org/poky-extras poky-extras - Cloning into 'poky-extras'... + $ git clone git://git.yoctoproject.org/meta-yocto-kernel-extras meta-yocto-kernel-extras + Cloning into 'meta-yocto-kernel-extras'... remote: Counting objects: 690, done. remote: Compressing objects: 100% (431/431), done. remote: Total 690 (delta 238), reused 690 (delta 238) @@ -223,10 +223,10 @@ information on BSP Layers. Tarball Extraction: You can download any released - BSP tarball from the same "Downloads" page of the + BSP tarball from the same "Downloads" page of the Yocto Project Website to get the Yocto Project release. - Once on the "Download" page, look for "BSP" under the + Once on the "Download" page, look for "BSP" under the "Type" heading. Once you have the tarball, just extract it into a directory of your choice. Again, this method just produces a snapshot of the BSP layer in the form -- cgit v1.2.3-54-g00ecf