[oe] [PATCH] bitbake.conf: rework FILESPATH generation.

[Chris Larson]

Heh, already sent this reply out, but from the wrong email address.
This time it should actually hit the list...

On Thu, Feb 19, 2009 at 4:41 PM, Denys Dmytriyenko <denis at denix.org> wrote:
> On Thu, Feb 19, 2009 at 04:28:52PM -0700, Chris Larson wrote:
>> From: Chris Larson <clarson at mvista.com>
>>
>> Rework FILESPATH generation to be done in bitbake.conf, avoiding the
>> confusion about it being in multiple places.  Adds FILESPATHBASE and
>> FILESPATHPKG which can be manipulated rather than manipulating FILESPATH
>> directly.
>>
>> One usage possibility:
>>
>> FILESPATHBASE =. "${TOPDIR}/files:"
>>
>> Which would let me provide a custom busybox config for this build by
>> copying the defconfig from the openembedded metadata into my
>> build/files/busybox-1.0/ directory, for example.
>
> Can you please provide more details on this example? Thanks.

Normally, all paths in FILESPATH are relative to FILE_DIRNAME, the
location of the recipe being operated against.  With this change, you
can place files which are in SRC_URI as file:// urls in paths relative
to other locations.

You can do package customizations via changes to file:// files without
mucking up the local clone of the openembedded repository.

My intent is to create a class to facilitate running make menuconfig
on your kernel and busybox, and retain those changes.  Today, people
either go into workdir and customize it there, but those changes are
lost when you clean the package, or they overwrite files in the
metadata repository, which can lead to conflicts, and is just all
around more annoying to work with.  It's better to be able to have per
build or site wide overrides of those files.
-- 
Chris Larson
clarson at kergoth dot com
clarson at mvista dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Software Engineer
MontaVista Software, Inc.