From 1cafae44ec5a6fb6d2f8d2e6ebb58dcfe890b44e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 8 Aug 2011 12:57:11 -0700 Subject: documentation/dev-manual/dev-manual-start.xml: Added to kernel source setup I added instruction on how to set up a bare clone of the linux yocto kernel files and then how to create a clone of the bare clone. Finally added a part about setting up the meta-kernel-dev repository. This setup should do it for those that want to modify the kernel and not have to download source files from the upstream everytime they make a change. (From yocto-docs rev: 90ae8249d119d5db17507eea37eb6deb0822a682) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-start.xml | 38 ++++++++++++++++++++------- 1 file changed, 29 insertions(+), 9 deletions(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 939ccef590..822731af90 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -75,7 +75,6 @@ $ tar xfj poky-1.1.tar.bz2 - This method does not produce a poky Git repository. You end up simply with a local snapshot of Yocto Project files that are based on the particular release in the tarball. @@ -108,20 +107,41 @@ Linux Yocto Kernel: If you are going to be making modifications to a supported Linux Yocto kernel you - need a local copy of these files. - Creating a local Git repository of the files allows you access to the files locally - and gives you opportunity to contribute changes upstream to the Yocto Project. - As an example, the following transcript shows how to clone the - linux-yocto-2.6.37 kernel Git repository: + need to get set up so that you can edit local copies of the source. + This setup involves creating a bare clone of the Linux Yocto kernel and then cloning + that repository. + As an example, the following transcript shows how to create the bare clone + of the linux-yocto-2.6.37 kernel and then create a clone of + that repository: - $ git clone git://git.yoctoproject.org/linux-yocto-2.6.37 - Initialized empty Git repository in /home/scottrif/linux-yocto-2.6.37/.git/ + $ git clone --bare git://git.yoctoproject.org/linux-yocto-2.6.37 linux-yocto-2.6.37.git + Initialized empty Git repository in /home/scottrif/poky/linux-yocto-2.6.37.git/ remote: Counting objects: 1886034, done. remote: Compressing objects: 100% (314326/314326), done. remote: Total 1886034 (delta 1570200), reused 1870337 (delta 1554798) - Receiving objects: 100% (1886034/1886034), 401.51 MiB | 3.99 MiB/s, done. + Receiving objects: 100% (1886034/1886034), 401.51 MiB | 3.27 MiB/s, done. Resolving deltas: 100% (1570200/1570200), done. + + Now create a clone of the bare clone just created: + + $ git clone linux-yocto-2.6.37.git linux-yocto-2.6.37 + Initialized empty Git repository in /home/scottrif/poky/linux-yocto-2.6.37/.git/ Checking out files: 100% (35188/35188), done. + + The final repository you need for kernel development is the + meta-kernel-dev Git repository. + This repository allows you to configure the build system so that you point to your + local area for the Linux Yocto kernel source files. + Pointing to these files locally is much more efficient than requiring a download of the + source files from upstream each time you build the kernel image: + + $ git clone git://git.yoctoproject.org/poky-extras poky-extras + Initialized empty Git repository in /home/scottrif/poky/poky-extras/.git/ + remote: Counting objects: 531, done. + remote: Compressing objects: 100% (471/471), done. + remote: Total 531 (delta 138), reused 307 (delta 39) + Receiving objects: 100% (531/531), 517.86 KiB, done. + Resolving deltas: 100% (138/138), done. Supported Board Support Packages (BSPs): The same considerations exist for BSPs. -- cgit v1.2.3-54-g00ecf