Re: Custom defconfig is not used

From: Diego Sueiro <diego.sueiro@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.org>
Subject: Re: Custom defconfig is not used
Date: Thu, 17 Oct 2013 07:39:10 -0300	[thread overview]
Message-ID: <CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

2013/10/17 Bruce Ashfield <bruce.ashfield@gmail.com>

> On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro <diego.sueiro@gmail.com>
> wrote:
> > Folks,
> >
> > Looking at log.do_unpack it shows:
> >
> > ...
> > NOTE: Unpacking
> >
> <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig
> > to
> >
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
> > ...
> >
> > NOTE: Unpacking
> > <...>/meta-mine/recipes-kernel/linux/linux-mainline-3.8/mine.patch to
> >
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
> > NOTE: Unpacking
> >
> <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig
> > to
> >
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
> >
> >
> > Note that it copies defconfig from meta-beagleboard and in the end,
> instead
> > copying mine, it is copying from meta-beagleboard again.
> >
> > My layer has the priority higher than meta-beagleboard.
>
> I can't get at my machines to test this myself (technically I'm still
> on vacation), but when you
> dump the bitbake environment, how many defconfig's show up in the
> SRC_URI ? It would be
> easy enough in your bbapend to simply call your defconfig something
> else (i.e. defconfig-mine)
> and override/append to kernel_do_configure() to simply copy yours over
> top of the .config,
> regardless of what the fetcher is doing with the SRC_URI.
>
> Bruce
>
>
Bruce,

Putting the following in my recipe did the trick:

do_configure_prepend() {
            cp ${WORKDIR}/defconfig-mine ${WORKDIR}/defconfig
}

Now the .config is the same as my custom defconfig.

But, this is a workaround, right?
I expected to get this working "out-of-box".
Why config fragments did not worked too?

--
*dS
Diego Sueiro

/*long live rock 'n roll*/

[-- Attachment #2: Type: text/html, Size: 3451 bytes --]