From caa6e079c316c70f3600114069654c459607e983 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 22 Apr 2013 09:16:29 -0700 Subject: [PATCH] dev-manual, bsp-guide: Updates for init-ifupdown change. Release 1.4 requires the user to create an append file to the new recipe init-ifupdown if they want to create their own custom /etc/network/interfaces file. Previously, they needed to append the netbase recipe. Changes needed in the migration section of the ref-manual as well as the exmaple used in the bsp-guide. (From yocto-docs rev: 1903df0c21dbc018f0dbb4ce90eac192b428606b) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/bsp-guide/bsp.xml | 50 ++++++++++++++++++++------ documentation/ref-manual/migration.xml | 18 ++++++++++ 2 files changed, 57 insertions(+), 11 deletions(-) diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index d5d87fa6fa..363ab77340 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -883,31 +883,59 @@ If you plan on customizing a recipe for a particular BSP, you need to do the following: - Include within the BSP layer a .bbappend - file for the modified recipe. - Place the BSP-specific file in the BSP's recipe - .bbappend file path under a directory named - after the machine. + Create a .bbappend + file for the modified recipe. + For information on using append files, see the + "Using .bbappend Files" + section in the Yocto Project Development Manual. + + + Ensure your directory structure in the BSP layer + that supports your machine is such that it can be found + by the build system. + See the example later in this section for more information. + + + Put the append file in a directory whose name matches + the machine's name and is located in an appropriate + sub-directory inside the BSP layer (i.e. + recipes-bsp, recipes-graphics, + recipes-core, and so forth). + + Place the BSP-specific files in the directory named for + your machine inside the BSP layer. + - To better understand this, consider an example that customizes a recipe by adding + Following is a specific example to help you better understand the process. + Consider an example that customizes a recipe by adding a BSP-specific configuration file named interfaces to the - netbase_5.0.bb recipe for machine "xyz". + init-ifupdown_1.0.bb recipe for machine "xyz". Do the following: - Edit the netbase_5.0.bbappend file so that it + Edit the init-ifupdown_1.0.bbappend file so that it contains the following: FILESEXTRAPATHS_prepend := "${THISDIR}/files:" PRINC := "${@int(PRINC) + 2}" - + + The append file needs to be in the + meta-xyz/recipes-core/init-ifupdown directory. + Create and place the new interfaces configuration file in the BSP's layer here: - meta-xyz/recipes-core/netbase/files/xyz/interfaces - + meta-xyz/recipes-core/init-ifupdown/files/xyz/interfaces + + The + FILESEXTRAPATHS + variable in the append files extends the search path + the build system uses to find files during the build. + Consequently, for this example you need to have the + files directory in the same location + as your append file. diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 7aefcfd08d..a7bab5aa36 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -335,6 +335,24 @@ +
+ Custom Interfaces File (netbase change) + + + If you have created your own custom + etc/network/interfaces file by creating + an append file for the netbase recipe, + you now need to create an append file for the + init-ifupdown recipe instead, which you can + find in the + Source Directory + at meta/recipes-core/init-ifupdown. + For information on how to use append files, see the + "Using .bbappend Files" + in the Yocto Project Development Manual. + +
+
Remote Debugging