From a19f575cde39917e4632dab1e813d84402f95937 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 11 Jun 2014 10:46:05 +0300 Subject: dev-manual, kernel-dev, ref-manual: Updated task name usage. There was inconsistency on how we refer to a task name throughout the YP manual set. The proper way is "do_". Some occurrences did not include the "do_" prefix. These have been fixed. (From yocto-docs rev: b32821bb0d3e6de7bca68b25c662a023526a10c4) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 79 ++++++++++++++-------- 1 file changed, 50 insertions(+), 29 deletions(-) (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 0c66a7c232..3922c8f0f4 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -3548,7 +3548,7 @@ As part of the kernel build process, the - kernel_configcheck task runs. + do_kernel_configcheck task runs. This task validates the kernel configuration by checking the final .config file against the input files. During the check, the task produces warning messages for the following @@ -3565,8 +3565,9 @@ In other words, the option does not appear anywhere. - The kernel_configcheck task can also optionally report - if an option is overridden during processing. + The do_kernel_configcheck task can + also optionally report if an option is overridden during + processing. @@ -3580,29 +3581,45 @@ To streamline the configuration, do the following: - Start with a full configuration that you know - works - it builds and boots successfully. - This configuration file will be your baseline. - Separately run the configme and - kernel_configcheck tasks. + Start with a full configuration that you + know works - it builds and boots successfully. + This configuration file will be your baseline. + + Separately run the + do_configme and + do_kernel_configcheck tasks. + Take the resulting list of files from the - kernel_configcheck task warnings and do the following: + do_kernel_configcheck task + warnings and do the following: - Drop values that are redefined in the fragment but do not - change the final .config file. - Analyze and potentially drop values from the - .config file that override required - configurations. - Analyze and potentially remove non-board specific options. + + Drop values that are redefined in the fragment + but do not change the final + .config file. + + + Analyze and potentially drop values from the + .config file that override + required configurations. + + + Analyze and potentially remove non-board + specific options. + + + Remove repeated and invalid options. - Remove repeated and invalid options. - After you have worked through the output of the kernel configuration - audit, you can re-run the configme - and kernel_configcheck tasks to see the results of your - changes. - If you have more issues, you can deal with them as described in the - previous step. + + After you have worked through the output of the kernel + configuration audit, you can re-run the + do_configme and + do_kernel_configcheck tasks to + see the results of your changes. + If you have more issues, you can deal with them as + described in the previous step. + @@ -5149,14 +5166,18 @@ Gateways via their Web Interfaces"
Handling a Package Name Alias - Sometimes a package name you are using might exist under an alias or as a similarly named - package in a different distribution. - The OpenEmbedded build system implements a distro_check + Sometimes a package name you are using might exist under + an alias or as a similarly named package in a different + distribution. + The OpenEmbedded build system implements a + do_distro_check task that automatically connects to major distributions and checks for these situations. - If the package exists under a different name in a different distribution, you get a - distro_check mismatch. - You can resolve this problem by defining a per-distro recipe name alias using the + If the package exists under a different name in a different + distribution, you get a distro_check + mismatch. + You can resolve this problem by defining a per-distro recipe + name alias using the DISTRO_PN_ALIAS variable. @@ -6922,7 +6943,7 @@ Gateways via their Web Interfaces" Returns "True" if pkg is in the installed package list of the image, which is based on the manifest file that is generated during the - do.rootfs task. + do_rootfs task. hasFeature(feature): Returns "True" if the feature is in -- cgit v1.2.3-54-g00ecf