How do I modifly kernel config?

How do I modifly kernel config?

[Peter Chubb]

Hi,
   Is there an easy way to make a recipe that builds a kernel with a
different .config ?  I know I can copy an entire recipe with my own
file://defconfig --- but is that the best way to proceed?
--
Dr Peter Chubb                              peter DOT chubb AT nicta.com.au
http://www.ertos.nicta.com.au           ERTOS within National ICT Australia
           Kernel Engineering Group (KEG): Where Systems Brew.

Re: How do I modifly kernel config?

[Christopher Larson]

Peter Chubb wrote:
> Hi,
>    Is there an easy way to make a recipe that builds a kernel with a
> different .config ?  I know I can copy an entire recipe with my own
> file://defconfig --- but is that the best way to proceed?

FILESPATHBASE =. "${TOPDIR}/files"

Then mkdir -p files/<PN for the kernel recipe>; cp myconfig files/<PN 
for the kernel recipe>/defconfig.  or what have you.  file:// uris are 
processed via FILESPATH, which is constructed by FILESPATHBASE and 
FILESPATHPKG.  The default FILESPATHBASE is the location where the 
recipe resides, if that helps explain it.

-Chris

Re: How do I modifly kernel config?

[Christopher Larson]

Christopher Larson wrote:
> Peter Chubb wrote:
>> Hi,
>>    Is there an easy way to make a recipe that builds a kernel with a
>> different .config ?  I know I can copy an entire recipe with my own
>> file://defconfig --- but is that the best way to proceed?
>
> FILESPATHBASE =. "${TOPDIR}/files"

Erm, make that FILESPATHBASE =. "${TOPDIR}/files:".  It's colon separated.

Re: How do I modifly kernel config?

[Peter Chubb]

>>>>> "Christopher" == Christopher Larson <clarson@mvista.com> writes:

Christopher> Christopher Larson wrote:
>> Peter Chubb wrote:
>>> Hi, Is there an easy way to make a recipe that builds a kernel
>>> with a different .config ?  I know I can copy an entire recipe
>>> with my own file://defconfig --- but is that the best way to
>>> proceed?
>> 
>> FILESPATHBASE =. "${TOPDIR}/files"

Christopher> Erm, make that FILESPATHBASE =. "${TOPDIR}/files:".  It's
Christopher> colon separated.

Thanks, but where do I put this?  In build/conf/local.conf?  or
somewhere else? (because it seems to be being ignored for me)

Peter C
--
Dr Peter Chubb                                  peter DOT chubb AT nicta.com.au
http://www.ertos.nicta.com.au               ERTOS within National ICT Australia
All things shall perish from under the sky/Music alone shall live, never to die

Re: How do I modifly kernel config?

[Chris Larson]

On Thu, Jun 11, 2009 at 3:33 AM, Peter Chubb<peter.chubb@nicta.com.au> wrote:
>>>>>> "Christopher" == Christopher Larson <clarson@mvista.com> writes:
>
> Christopher> Christopher Larson wrote:
>>> Peter Chubb wrote:
>>>> Hi, Is there an easy way to make a recipe that builds a kernel
>>>> with a different .config ?  I know I can copy an entire recipe
>>>> with my own file://defconfig --- but is that the best way to
>>>> proceed?
>>>
>>> FILESPATHBASE =. "${TOPDIR}/files"
>
> Christopher> Erm, make that FILESPATHBASE =. "${TOPDIR}/files:".  It's
> Christopher> colon separated.
>
> Thanks, but where do I put this?  In build/conf/local.conf?  or
> somewhere else? (because it seems to be being ignored for me)

Local.conf is fine, yes.  It's unlikely that it's actually being
ignored, though.  Run a bitbake -e|grep FILESPATH=, and see what it's
set to.  Note that it will only list the items in the search path that
actually exist, so ensure you mkdir the ${TOPDIR}/files directory
referred to there.  Also note that the default TOPDIR is $PWD, which
is where you're building from, which is most commonly your build
directory.
-- 
Chris Larson
clarson at kergoth dot com
clarson at mvista dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Software Engineer
MontaVista Software, Inc.

Re: How do I modifly kernel config?

[Peter Chubb]

>>>>> "Chris" == Chris Larson <clarson@kergoth.com> writes:

>> Thanks, but where do I put this?  In build/conf/local.conf?  or
>> somewhere else? (because it seems to be being ignored for me)

Chris> Local.conf is fine, yes.  It's unlikely that it's actually
Chris> being ignored, though.  Run a bitbake -e|grep FILESPATH=, and
Chris> see what it's set to.  Note that it will only list the items in
Chris> the search path that actually exist, so ensure you mkdir the
Chris> ${TOPDIR}/files directory referred to there.  Also note that
Chris> the default TOPDIR is $PWD, which is where you're building
Chris> from, which is most commonly your build directory.

Thanks.  I'd gone and misspelled linux-omap as linux_omap and that was
the problem.


--
Dr Peter Chubb                              peter DOT chubb AT nicta.com.au
http://www.ertos.nicta.com.au           ERTOS within National ICT Australia
           Kernel Engineering Group (KEG): Where Systems Brew.