diff options
| author |   Scott Rifenbark <srifenbark@gmail.com> | 2016-06-06 13:25:18 -0700 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-06-06 22:53:35 +0100 |
| commit | 9c75c64cb99a3d5103b7bb4e2a700e5bb5af516b (patch) | |
| tree | eb732c97330d67ec39dbe66f9b4dc7a2a31abc95 /documentation | |
| parent | 25d8fac2d30f658d56ee2d27e299a560b6731299 (diff) | |
| download | openembedded-core-contrib-9c75c64cb99a3d5103b7bb4e2a700e5bb5af516b.tar.gz | |
kernel-dev: Fix the locations of .config and source directory
The locations of the kernel .config file and source direcotry
moved a couple releases ago. Updated the documentation
accordingly.
Also added a note explaining how to check the expansion of
variables, which servs a couple of purposes:
* For curious readers, shows them how to understand where
these variables come from and how they are used.
* For suspicious readers, shows them how they can verify that
the variables in the documentation are actually correct.
Author: Tom Zanussi <tom.zanussi@linux.intel.com>
(From yocto-docs rev: a4f92870e70cb625f2987a59aff3f460457b4889)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/kernel-dev/kernel-dev-common.xml | 27 |
1 files changed, 22 insertions, 5 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index 261471c46b..a9aafd3c21 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -384,9 +384,10 @@ <para> The resulting <filename>.config</filename> file is - located in - <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink><filename>}</filename> under the - <filename>linux-${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink><filename>}-${<ulink url='&YOCTO_DOCS_REF_URL;#var-LINUX_KERNEL_TYPE'><filename>LINUX_KERNEL_TYPE</filename></ulink>}-build</filename> directory. + located in the build directory, + <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-B'><filename>B</filename></ulink><filename>}</filename>, + which expands to + <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink><filename>}</filename><filename>/linux-</filename><filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink><filename>}-${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-LINUX_KERNEL_TYPE'><filename>LINUX_KERNEL_TYPE</filename></ulink><filename>}-build</filename>. You can use the entire <filename>.config</filename> file as the <filename>defconfig</filename> file as described in the "<link linkend='changing-the-configuration'>Changing the Configuration</link>" section. @@ -394,6 +395,16 @@ see the "<ulink url='&YOCTO_DOCS_DEV_URL;#using-menuconfig'>Using <filename>menuconfig</filename></ulink>" section in the Yocto Project Development Manual. + <note> + You can determine what a variable expands to by looking + at the output of the <filename>bitbake -e</filename> + command: + <literallayout class='monospaced'> + $ bitbake -e virtual/kernel + </literallayout> + Search the output for the variable in which you are + interested to see exactly how it is expanded and used. + </note> </para> <para> @@ -512,8 +523,14 @@ </literallayout> Taking this step ensures you have the sources prepared and the configuration completed. - You can find the sources in the - <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink><filename>}/linux</filename> directory. + You can find the sources in the build directory within the + <filename>source/</filename> directory, which is a symlink + (i.e. <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-B'><filename>B</filename></ulink><filename>}/source</filename>). + The <filename>source/</filename> directory expands to + <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink><filename>}</filename><filename>/linux-</filename><filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink><filename>}-${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-LINUX_KERNEL_TYPE'><filename>LINUX_KERNEL_TYPE</filename></ulink><filename>}-build/source</filename>. + The directory pointed to by the + <filename>source/</filename> symlink is also known as + <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-STAGING_KERNEL_DIR'><filename>STAGING_KERNEL_DIR</filename></ulink><filename>}</filename>. </para> <para> |