From: Scott Rifenbark Date: Fri, 22 Sep 2017 20:30:11 +0000 (-0700) Subject: ref-manual: Updated link formatting in KBUILD_DEFCONFIG variable. X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cc601ade6f6355b6852680d30e3965702a8db8d3;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git ref-manual: Updated link formatting in KBUILD_DEFCONFIG variable. (From yocto-docs rev: ba2aa642c3c1696a155b07840f84b8b3f0e692b5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 6f8721199bb..bd5e8c90162 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -7043,20 +7043,23 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Typically, when using a defconfig to configure a kernel during a build, you place the file in your layer in the same manner as you would - patch files and configuration fragment files (i.e. + place patch files and configuration fragment files (i.e. "out-of-tree"). However, if you want to use a defconfig file that is part of the kernel tree (i.e. "in-tree"), you can use the - KBUILD_DEFCONFIG variable to point - to the defconfig file. + KBUILD_DEFCONFIG variable and append + the + KMACHINE + variable to point to the defconfig + file. To use the variable, set it in the append file for your kernel recipe using the following form: - KBUILD_DEFCONFIG_KMACHINE ?= defconfig_file + KBUILD_DEFCONFIG_KMACHINE ?= defconfig_file Here is an example from a "raspberrypi2" KMACHINE build that uses a