From b643938bdecd4ed928713c3a9b4c9f7e0e637964 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 29 Jun 2017 15:54:35 -0700 Subject: dev-manual, kernel-dev: Moved the kernel build hierarchy section Fixes [YOCTO #11630] The section that presented the Yocto Linux kernel file structure resulting from a build using BitBake needed to be in the kernel-dev manual. I moved it over. This required transferring over a figure as well. (From yocto-docs rev: 0abc6c7d87a6aa10dac28fefbb280eb51fea61a7) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 71 ++------------------------- 1 file changed, 3 insertions(+), 68 deletions(-) (limited to 'documentation/dev-manual/dev-manual-model.xml') diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 05ff369f5d..0055bccfed 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -82,71 +82,6 @@ Yocto Project Linux Kernel Development Manual. -
- Kernel Overview - - - Upstream storage of all the available kernel source code is - one thing, while representing and using the code on your host - development system is another. - Conceptually, you can think of the kernel source repositories - as all the source files necessary for all the supported - Yocto Linux kernels. - As a developer, you are just interested in the source files - for the kernel on which you are working. - And, furthermore, you need them available on your host system. - - - - Kernel source code is available on your host system a couple - of different ways. - If you are working in the kernel all the time, you probably - would want to set up your own local Git repository of the - Yocto Linux kernel tree. - If you just need to make some patches to the kernel, you can - access temporary kernel source files that were extracted and - used during a build. - We will just talk about working with the temporary source code. - For more information on how to get kernel source code onto your - host system, see the - "Setting Up to Work On a Kernel" - section. - - - - What happens during the build? - When you build the kernel on your development system, all files needed for the build - are taken from the source repositories pointed to by the - SRC_URI variable - and gathered in a temporary work area - where they are subsequently used to create the unique kernel. - Thus, in a sense, the process constructs a local source tree specific to your - kernel to generate the new kernel image - a source generator if you will. - - - - The following figure shows the temporary file structure - created on your host system when the build occurs. - This - Build Directory - contains all the source files used during the build. - - - - - - - - Again, for additional information on the Yocto Project kernel's - architecture and its branching strategy, see the - Yocto Project Linux Kernel Development Manual. - You can also reference the - "Patching the Kernel" - section for a detailed example that modifies the kernel. - -
-
Kernel Modification Workflow @@ -219,9 +154,9 @@ Try to resist the temptation to directly edit an existing .config file, which is found in the Build Directory among the source code - used for the build (e.g. see the bottom - illustration in the - "Kernel Overview" + used for the build (e.g. see the workflow illustration + in the + "Kernel Modification Workflow" section). Doing so, can produce unexpected results when the OpenEmbedded build system regenerates the configuration -- cgit v1.2.3-54-g00ecf