diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 331700bdea..880a429317 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1136,7 +1136,7 @@ -
+
Writing a New Recipe @@ -1426,7 +1426,7 @@ extracted during the do_unpack task. For another example that specifies these types of files, see the - "Autotooled Package" + "Autotooled Package" section. @@ -1522,7 +1522,7 @@ The directories are assumed to be subdirectories of the directory in which the recipe or append file resides. For another example that specifies these types of files, see the - "Single .c File Package (Hello World!)" + "Single .c File Package (Hello World!)" section. @@ -1716,15 +1716,13 @@ Configuring the Recipe + Configuration, such as build-time or runtime dependencies, + is typically accomplished by running a configure script with + some options, or by modifying a build configuration file. Most software provides some means of setting build-time configuration options before compilation. - Typically, setting these options is accomplished by running a - configure script with some options, or by modifying a build - configuration file. - - It is possible that required build-time or runtime dependencies - exist in the software's documentation. - + You can often find build-time or runtime dependencies in the + software's documentation. @@ -1849,14 +1847,15 @@ or nativesdk only. The failure occurs when the compilation process uses improper headers, libraries, or other files from the - host system during cross-compiling for the target. + host system when cross-compiling for the target. - To fix the problem, you should be able to see + To fix the problem, examine the + log.do_compile file to identify the host paths being used (e.g. /usr/include, - /usr/lib, and so forth) by - examining the log.do_compile - file. + /usr/lib, and so forth) and then + either add configure options, apply a patch, or do both. + Failure to find required libraries/headers: If a build-time dependency is missing because it has @@ -1911,14 +1910,15 @@ Consequently, you do not have to have a do_install task as part of your recipe. + You just need to make sure the install portion of the + build completes with no issues. However, if you wish to install additional files not already being installed by make install, you should do this using a do_install_append function using the install command as described in Manual later in this list. - You just need to make sure the install portion of the - build completes with no issues. + Other (using make install): You need to define a @@ -1935,7 +1935,7 @@ For an example recipe using make install, see the - "Makefile-Based Package" + "Makefile-Based Package" section. Manual: You need to define a @@ -2030,7 +2030,8 @@ - Here are some examples: + The OpenEmbedded build system provides support for two + different ways of starting services: SysVinit: SysVinit is a system and service manager that @@ -2040,8 +2041,8 @@ started by the Linux kernel when the system boots. Init then controls the startup, running and shutdown of all other programs. - To include this service, your recipe needs to - inherit the + To enable a service using SysVinit, your recipe + needs to inherit the update-rc.d class. The class helps facilitate safely installing the @@ -2059,11 +2060,12 @@ homepage at . - To include this service, your recipe needs to - inherit the systemd class. - See the - systemd.bbclass - file or the + To enable a service using Systemd, your recipe + needs to inherit the systemd class. + See the systemd.bbclass file + located in your + Source Directory + in meta/classes or the "systemd.bbclass" section for more information. @@ -2109,12 +2111,12 @@ For an example showing how to install a post-installation script, see the - "Post-Installation Scripts" + "Post-Installation Scripts" section.
-
+
Post-Installation Scripts @@ -2180,10 +2182,9 @@ - Equivalent support for pre-install, - pre-uninstall, and - post-uninstall scripts exist - by way of pkg_preinst, + Equivalent support for pre-install, pre-uninstall, and + post-uninstall scripts exist by way of + pkg_preinst, pkg_prerm, and pkg_postrm, respectively. These scrips work in exactly the same way as does @@ -2208,7 +2209,7 @@ For information on how to customize your image by adding specific packages, see the - "Customizing Images Using Custom Package Groups" + "Customizing Images" section.
@@ -2227,7 +2228,7 @@ -
+
Single .c File Package (Hello World!) @@ -2276,7 +2277,7 @@
-
+
Autotooled Package Applications that use Autotools such as autoconf and @@ -2311,7 +2312,7 @@
-
+
Makefile-Based Package @@ -2401,7 +2402,7 @@ PR = "r3" PE = "1" - XORG_PN = "libxpm" + XORG_PN = "libXpm" PACKAGES =+ "sxpm cxpm" FILES_cxpm = "${bindir}/cxpm"