diff options
Diffstat (limited to 'handbook/ref-classes.xml')
| -rw-r--r-- | handbook/ref-classes.xml | 35 |
1 files changed, 18 insertions, 17 deletions
diff --git a/handbook/ref-classes.xml b/handbook/ref-classes.xml index 1cef9012c1..bec0814daf 100644 --- a/handbook/ref-classes.xml +++ b/handbook/ref-classes.xml @@ -266,19 +266,20 @@ autotools_stage_all <title>Python extensions - <filename>distutils.bbclass</filename></title> <para> - Recipes for Python extensions are simple - usually needs only - pointing to source archive and inheriting of proper bbclass. - Building is split into two methods dependly on method used by - module authors. + Recipes for Python extensions are simple - they usually only + require pointing to the source archive and inheriting the proper + bbclasses. + Building is split into two methods depending on the build method + used by the module authors. </para> - + <para> - Extensions which use autotools based build system require using + Extensions which use autotools based build system require use of autotools and distutils-base bbclasses in their recipes. </para> <para> - Extensions which use distutils build system require using + Extensions which use distutils build system require use of <filename>distutils.bbclass</filename> in their recipes. </para> @@ -300,12 +301,12 @@ autotools_stage_all <title>Packaging - <filename>package*.bbclass</filename></title> <para> - The packaging classes add support for generating packages from the output - from builds. The core generic functionality is in - <filename>package.bbclass</filename>, code specific to particular package - types is contained in various sub classes such as - <filename>package_deb.bbclass</filename> and <filename>package_ipk.bbclass</filename>. - Most users will + The packaging classes add support for generating packages from a builds + output. The core generic functionality is in + <filename>package.bbclass</filename>, code specific to particular package + types is contained in various sub classes such as + <filename>package_deb.bbclass</filename> and <filename>package_ipk.bbclass</filename>. + Most users will want one or more of these classes and this is controlled by the <glossterm> <link linkend='var-PACKAGE_CLASSES'>PACKAGE_CLASSES</link></glossterm> variable. The first class listed in this variable will be used for image @@ -319,15 +320,15 @@ autotools_stage_all <title>Building kernels - <filename>kernel.bbclass</filename></title> <para> - This class handle building of Linux kernels and the class contains code to know how to build both 2.4 and 2.6 kernel trees. All needed headers are + This class handles building of Linux kernels and the class contains code to know how to build both 2.4 and 2.6 kernel trees. All needed headers are staged into <glossterm><link linkend='var-STAGING_KERNEL_DIR'>STAGING_KERNEL_DIR</link></glossterm> directory to allow building of out-of-tree modules using <filename>module.bbclass</filename>. </para> <para> - The means that each kerel module built is packaged separately and inter-modules dependencies are + The means that each kerel module built is packaged separately and inter-module dependencies are created by parsing the <command>modinfo</command> output. If all modules are - required then installing "kernel-modules" package will install all + required then installing the "kernel-modules" package will install all packages with modules and various other kernel packages such as "kernel-vmlinux" are also generated. </para> @@ -377,7 +378,7 @@ autotools_stage_all packages generated by Poky. There are an ever increasing range of checks this makes, checking for common problems which break builds/packages/images, see the bbclass file for more information. Its usually up to distribution - policy to include this class (Poky doesn't at the time of writing but plans + policy to include this class (Poky does). to soon). </para> </section> |