From 8eb706a41b040cf1397c2ebe5517c40031f4d1fb Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 14 Oct 2014 06:57:45 -0700 Subject: ref-manual, dev-manual: Applied migration review edits. Applied the full set of first draft revision edits for the new migration section for 1.7. Comments from Paul Eggleton. (From yocto-docs rev: 90586addbc719ecaf7c768b267adf0e988e27b74) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/migration.xml | 85 +++++++++++++++------------------- 1 file changed, 38 insertions(+), 47 deletions(-) (limited to 'documentation/ref-manual/migration.xml') diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 864c489251..dd8c3e00cc 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -1710,17 +1710,19 @@ class changes occurred: - A separate build directory in Autotools recipes is - handled: + A separate build directory is now used by default: The autotools class has been changed to use a directory for building (B), which is separate from the source directory (S). - If the software being built is already capable of + This is commonly referred to as + B != S, or an out-of-tree build. + If the software being built is already capable of building in a directory separate from the source, you do not need to do anything. - However, if this capability does not exist, you will + However, if the software is not capable of being built + in this manner, you will need to either patch the software so that it can build separately, or you will need to change the recipe to inherit the @@ -1728,25 +1730,24 @@ class instead of the autotools class. - Handle "foreign": - The --foreign option is no longer - passed to automake when running - autoreconf. + The ‐‐foreign option is + no longer passed to automake when + running autoconf: This option tells automake that a particular software package does not follow the GNU standards and therefore should not be expected to distribute certain files such as ChangeLog, AUTHORS, and so forth. - The majority of upstream software packages already tell - automake these packages are foreign - and thus this option is mostly superfluous. + Because the majority of upstream software packages already + tell automake to enable foreign mode + themselves, the option is mostly superfluous. However, some recipes will need patches for this change. You can easily make the change by patching configure.ac so that it passes "foreign" to AM_INIT_AUTOMAKE(). See - + this commit for an example showing how to make the patch. @@ -1757,12 +1758,12 @@ Binary Configuration Scripts Disabled - Some of the core recipes that previously packaged binary - configuration scripts now disable the scripts instead due to the + Some of the core recipes that package binary configuration scripts + now disable the scripts instead due to the scripts previously requiring error-prone path substitution. Software that links against these libraries using these scripts - should use the much more robust - pkg-config instead. + should use the much more robust pkg-config + instead. The list of recipes changed in this version (and their configuration scripts) is as follows: @@ -1787,12 +1788,10 @@ pth (pth-config) taglib (taglib-config) - - Support for pkg-config has been added to - some recipes in the previous list in the rare cases - where the upstream software package does not already provide - it. - + Additionally, support for pkg-config has been + added to some recipes in the previous list in the rare cases + where the upstream software package does not already provide + it. @@ -1811,15 +1810,15 @@ - glibc 2.20 also minimally requires version - 2.6.32 of the Linux kernel. + glibc 2.20 requires version 2.6.32 or greater + of the Linux kernel. Thus, older kernels will no longer be usable in conjunction with it. For full details on the changes in glibc 2.20, - see the upstream release notes at - . + see the upstream release notes + here. @@ -1829,33 +1828,25 @@ The module_autoload_* - and - module_conf_* - variables have been replaced with the variables + variable is now deprecated and a new KERNEL_MODULE_AUTOLOAD - and - KERNEL_MODULE_PROBECONF, - respectively. - These variables no longer require you to specify the module name + variable should be used instead. + Also, + module_conf_* + must now be used in conjunction with a new + KERNEL_MODULE_PROBECONF + variable. + The new variables no longer require you to specify the module name as part of the variable name. This change not only simplifies usage but also allows the values of these variables to be appropriately incorporated into task signatures and thus trigger the appropriate tasks to re-execute when changed. You should replace any references to - module_autoload_* or - module_conf_* with the new variables. - - While it is recommended that you replace occurrences of the - module_conf_* variable with the - KERNEL_MODULE_PROBECONF variable, the - OpenEmbedded build system still recognizes the - module_conf_* variable. - However, you must be sure that any module name used in the - override with the module_conf variable - is included in the KERNEL_MODULE_PROBECONF - variable. - + module_autoload_* with + KERNEL_MODULE_AUTOLOAD, and add any modules + for which module_conf_* is specified to + KERNEL_MODULE_PROBECONF. @@ -1863,7 +1854,7 @@ KERNEL_MODULE_AUTOLOAD and KERNEL_MODULE_PROBECONF - descriptions in the variable's glossary. + variables. -- cgit v1.2.3-54-g00ecf