1962 2012-02-06 11:59:03 +0000 Ensure BSP developer guide recommends appropriate techniques to ensure MACHINE specific changes are packages thus 2012-04-18 12:07:28 +0000 1 1 9 Documentation Quick Start quick-start unspecified x86 Multiple VERIFIED FIXED http://git.yoctoproject.org/cgit.cgi/yocto-docs/commit/?id=f5e51d60312d9335a790023f193cae1ba76277ae 17-april-2012: verified/fixed Medium normal 1.2 1 josh srifenbark jessica.zhang msm-oss poky.doc.watcher poky.watcher tom.zanussi --- --- --- oldest_to_newest 18511 0 josh 2012-02-06 11:59:03 +0000 Whilst reviewing a recent BSP submission I noticed that the netbase customisation was making a MACHINE specific change but wasn't marked as thus. Therefore, should a user have the layer enabled but build for a different BSP of the same architecture they could still end up with the netbase changes. The base.bbclass includes a mechanism to try and ensure that MACHINE specific changes generate MACHINE specific packages. If a file is fetched from a directory named for the MACHINE[1] i.e.: meta-mymachine/recipes-core/netbase/files/mymachine/interfaces See [2] for a real world example. We need to ensure that these subtleties are documented in the BSP manual, and also be aware of them when reviewing BSP's for inclusion. 1. http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/base.bbclass#n459 2. http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-core/netbase/netbase-4.47/beagleboard 19828 1 dvhart 2012-04-03 17:38:56 +0000 Do, the BSP developer guide should have a blurb as follows: When customizing a recipe for a particular BSP, such as adding a BSP specific configuration file, a bbappend for the recipe should be included in the BSP layer and the BSP specific file should be placed in a directory of the same name as the MACHINE defined by the BSP layer. For example, to change the interfaces file for the netbase recipe for machine "xyz" the new interfaces file should be placed as follows: meta-xyz/recipes-core/netbase/files/xyz/interfaces And the bbappend should contain: $ cat meta-xyz/recipes-core/netbase/netbase_4.47.bbappend FILESEXTRAPATHS_prepend := "${THISDIR}/files:" PRINC := "${@int(PRINC) + 2}" Correct Joshua? 19886 2 josh 2012-04-04 17:48:51 +0000 Looks OK to me. 19888 3 dvhart 2012-04-04 17:53:11 +0000 Great, assigning to Scott to integrate the changes. Scott, can you accept this bug and pull in the changes from comment 1. 19896 4 srifenbark 2012-04-04 18:55:22 +0000 Darren, I will implement this fix. Scott 19900 5 msm-oss 2012-04-04 19:08:09 +0000 It would be nice to have a net-tools_*bbappend example which shows static configuring a network interface. 19905 6 srifenbark 2012-04-04 21:04:02 +0000 New section added called "Customizing a Recipe for a BSP". The section is based on Darren's Comment #1. Can be seen at http://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html#customizing-a-recipe-for-a-bsp 19907 7 srifenbark 2012-04-04 21:07:11 +0000 If we want something on net-tools_*bbappend example which shows static configuring a network interface, then I will need more information. Also, would this fit just as a second example in the new section I created? I marked this bug resolved. If we do want to add another example based on Matthew's suggestion the bug can be re-opened. Scott 19909 8 msm-oss 2012-04-04 21:27:44 +0000 (In reply to comment #7) > If we want something on net-tools_*bbappend example which shows static > configuring a network interface, then I will need more information. Also, > would this fit just as a second example in the new section I created? I marked > this bug resolved. If we do want to add another example based on Matthew's > suggestion the bug can be re-opened. > > Scott I'll look at writing a patch to add a net-tools example at some point. -M 19910 9 srifenbark 2012-04-04 21:29:36 +0000 This sounds like a plan Matt... thanks. Scott 20603 10 josh 2012-04-18 00:43:16 +0000 Verify manual section added 20643 11 srifenbark 2012-04-18 12:07:28 +0000 I changed the whiteboard comment to reflect the bug as verified/fixed.