User:CesarB/Using a local overlay
From Openmoko
(Updated for 2007.2; not tested yet) |
m (→Creating a local overlay: typo) |
||
Line 20: | Line 20: | ||
BBFILE_PATTERN_local = "^${OMDIR}/local/packages/" | BBFILE_PATTERN_local = "^${OMDIR}/local/packages/" | ||
BBFILE_PRIORITY_upstream = "5" | BBFILE_PRIORITY_upstream = "5" | ||
− | + | BBFILE_PRIORITY_local = "10" | |
The <code>BBFILE_PRIORITY_local</code> value should be greater than the <code>BBFILE_PRIORITY_upstream</code> value. | The <code>BBFILE_PRIORITY_local</code> value should be greater than the <code>BBFILE_PRIORITY_upstream</code> value. |
Revision as of 06:53, 26 August 2007
A local overlay is a way to add your own bitbake recipes (or override the ones from openembedded) without having them clobbered when you update these trees.
Contents |
Creating a local overlay
To create a local overlay:
- Create a directory for it and its subdirectories
mkdir local local/conf local/classes local/packages
- Copy
site.conf
from the openmoko tree tolocal/conf
cp build/conf/site.conf local/conf/site.conf
- Edit the local.conf you copied to add the new tree as a source for bitbake recipes. You must change the
BBFILES
variable, and add theBBFILE_COLLECTIONS
,BBFILE_PATTERN_*
andBBFILE_PRIORITY_*
variables:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb" BBFILE_COLLECTIONS = "upstream local" BBFILE_PATTERN_upstream = "^${OMDIR}/openembedded/packages/" BBFILE_PATTERN_local = "^${OMDIR}/local/packages/" BBFILE_PRIORITY_upstream = "5" BBFILE_PRIORITY_local = "10"
The BBFILE_PRIORITY_local
value should be greater than the BBFILE_PRIORITY_upstream
value.
While you are at it, you could change the SOURCEFORGE_MIRROR
variable to a nearby mirror.
- Change your
BBPATH
environment variable to add the new tree before the two others (for MokoMakefile, the variable is on thesetup-env
file).
export BBPATH="${OMDIR}/local:${OMDIR}/build:${OMDIR}/openembedded"
Using a local overlay
How you use the local overlay depends on which part of the tree you want to affect.
Changing files in conf/
To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.
Changing files in classes/
To change a file in classes/, just copy the file to the overlay tree and edit it.
Changing packages
Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also all the files it includes with require
, and the FILESDIR
directories (all directories referred to by FILESDIR
, usually named either package-version or files
). If you forget one of them, the build will give an error (either when parsing the recipe in the case of require
, or when trying to build in the case of the FILESDIR
directories).
Adding a new package
You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.