From 374a5388cdc8625d4333b9deead70c1553fb88c2 Mon Sep 17 00:00:00 2001 From: Jacob Godserv Date: Thu, 21 Jan 2010 13:19:33 -0500 Subject: [PATCH 9/9] In cross-compiling-kernel.xml, small wording fix for kernel source installation, and additional explanation for INSTALL_MOD_PATH --- .../embedded/handbook/cross-compiling-kernel.xml | 15 +++++++++++---- 1 files changed, 11 insertions(+), 4 deletions(-) diff --git a/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml b/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml index 39f351e..505052e 100644 --- a/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml +++ b/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml @@ -25,10 +25,10 @@ compiling is all the same.

You should install the kernel into the sysroot so that if you want to -cross-compile packages which include kernel modules, the process should be -transparent. If you don't need such packages, then of course the actual place -where you build the kernel does not matter. Some people build all their -kernels in /usr/src/ for example. +cross-compile packages which include kernel modules, the process will be +transparent. Otherwise, the actual place where you build the kernel does +not matter. Some people build all their kernels in /usr/src/ +for example.

@@ -64,6 +64,13 @@ chop off that trailing gcc and that's what you use:

+There is an additional variable, INSTALL_MOD_PATH, which defines where +the /lib directory will be created, and all the modules stored. +While you don't have to transfer the kernel sources to your target device, +if you build any modules, you'll want this directory. +

+ +

There are really two ways you can setup the system. You can modify the toplevel Makefile or you can override the relevant variables on the command line. How you do it is largely a matter of taste, so we'll cover both. Pick -- 1.6.4.4