Bruce,

We have two scenarios here:
  1. bbapend with full defconfig replacement
  2. bbapend with config fragments
The first scenario just worked when using FILESPATH_prepend. For me it does not make sense, since on YP manual says that FILESEXTRAPATHS_prepend must be use [1].

The second scenario did not worked even changing to FILESPATH_prepend.


[1] - http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-FILESEXTRAPATHS



Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


2013/10/25 Mike Lewis <mikelewis@alphalem.com>
Bruce: yep, fixed my issue. Sorry for the bother!

Diego: thanks for the solution!

- Mike


On 10/25/2013 11:44 AM, Bruce Ashfield wrote:
On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
Bruce,

Regarding the defconfig not used, I've found this thread on Angstrom devel
ML:
http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html

I've replaced "FILESEXTRAPATHS_prepend" with "FILESPATH_prepend" and removed
the custom "do_configure_prepend" function and bitbake is now using my
defconfig.
So, it seems that there is an issue with FILESEXTRAPATHS variable.

Aha. That does make sense.

Mike: does that same change fix your issues ?

Bruce

Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com>
On 13-10-22 12:23 PM, Mike Lewis wrote:
Hi Bruce,

I'm trying to accomplish the nearly the same thing (i.e. adding config
fragment) and I'm having the same issue at the do_patch step. Were you
able to reproduce this on your end?

Mike,

Is you config/layer somewhere than I can have a look at it ? I was trying
some builds here, and my tests are working. But I'd like to try it
with your config as well.

Bruce


Thanks,
Mike

On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
On 13-10-18 05:17 AM, Diego Sueiro wrote:

2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
<mailto:bruce.ashfield@windriver.com>>

     I fell behind today .. i had 2300 unread email to start this
morning :)
     Is there a way that I can get a copy of your recipes and layers ?
If
     I can do a build myself, I can easily debug and fix this ..
     otherwise, we'll
     go back and forth many times debugging.

     Cheers,

     Bruce


I'm using the environment provided by Angstrom from it's github setup
scripts.
If you want to exactly reproduce it you need to:

     git clone
https://github.com/Angstrom-distribution/setup-scripts.git
     cd setup-scripts
     git checkout angstrom-v2013.06-yocto1.4
     MACHINE=beaglebone ./oebb.sh config beaglebone

Here is the setup and files for meta-mine:

bblayers.conf:

     BBLAYERS = \"

         ...
         ${TOPDIR}/sources/meta-mine \
         "

meta-mine/conf/layer.conf:

     # We have a conf and classes directory, append to BBPATH
     BBPATH .= ":${LAYERDIR}"
     # We have a recipes directory, add to BBFILES
     BBFILES += "${LAYERDIR}/recipes*/*/*.bb
     ${LAYERDIR}/recipes*/*/*.bbappend"
     BBFILE_COLLECTIONS += "mine-layer"
     BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
     BBFILE_PRIORITY_mine-layer = "10"
     LAYERDEPENDS_mine-layer = "angstrom-layer"

meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:

     FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.8:"
     inherit kernel
     require recipes-kernel/linux/linux-yocto.inc
     COMPATIBLE_MACHINE_beaglebone = "(beaglebone)"
     SRC_URI += " file://config-addons.cfg "

meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:

     CONFIG_WATCHDOG_NOWAYOUT=y
     CONFIG_NTFS_FS=y
     CONFIG_NTFS_RW=y



But I think that instead of using the whole Angstrom you can just use
poky and meta-beagleboard/common-bsp on dylan branch.

Great. I'll launch some test builds and see what breaks (or works) :)

Bruce


Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto