Embedding Custom Packages - Revision history

Henryk: Embed Custom Packages moved to Embedding Custom Packages

2007-07-12T03:12:36Z

Embed Custom Packages moved to Embedding Custom Packages

← Older revision	Revision as of 03:12, 12 July 2007
(No difference)

Henryk at 21:38, 10 July 2007

2007-07-10T21:38:24Z

@@ Line 1: / Line 1: @@
 The easiest and cleanest way to embed custom packages into an OpenMoko image build is to basically create a custom distribution on top of OpenMoko (just like OpenMoko is built on top of OpenEmbedded). In order to do this we create a new directory tree <code>openmoko-sar</code> next to <code>oe</code> and <code>openembedded</code>:
  $OPENMOKODIR
@@ Line 32: / Line 34: @@
 and in <code>build/conf/local.conf</code> append:
  BBFILES := "${BBFILES} ${OMDIR}/openmoko-sar/packages/*/*.bb"

Henryk at 21:34, 10 July 2007

2007-07-10T21:34:56Z

← Older revision		Revision as of 21:34, 10 July 2007
Line 25:		Line 25:

	For a first test we will put our own image recipes into this tree, and create the new recipes based on the image recipes from <code>$OPENMOKODIR/oe/packages/images/</code>. Simply copy the existing recipes, change their name, modify the <code>require</code> statement in (the now new) <code>openmoko-sar-devel-image.bb</code>. At a later time we plan to put this structure into a version control system.		For a first test we will put our own image recipes into this tree, and create the new recipes based on the image recipes from <code>$OPENMOKODIR/oe/packages/images/</code>. Simply copy the existing recipes, change their name, modify the <code>require</code> statement in (the now new) <code>openmoko-sar-devel-image.bb</code>. At a later time we plan to put this structure into a version control system.

			To actually use this structure the following changes are necessary. In <code>setup-env</code> change:
			export BBPATH="${OMDIR}/build:${OMDIR}/oe:${OMDIR}/openembedded:"
			to
			export BBPATH="${OMDIR}/build:${OMDIR}/oe:${OMDIR}/openembedded:${OMDIR}/openmoko-sar"
			and in <code>build/conf/local.conf</code> append:
			BBFILES := "${BBFILES} ${OMDIR}/openmoko-sar/packages//.bb"

Henryk at 21:33, 10 July 2007

2007-07-10T21:33:22Z

New page

The easiest and cleanest way to embed custom packages into an OpenMoko image build is to basically create a custom distribution on top of OpenMoko (just like OpenMoko is built on top of OpenEmbedded). In order to do this we create a new directory tree <code>openmoko-sar</code> next to <code>oe</code> and <code>openembedded</code>:
$OPENMOKODIR
|
|-> oe
| |
| |-> classes
| | |
| | |-> ...
| |-> packages
| | |
| | |-> images
| | |-> ...
| |->...
|-> openembedded
| |
| |->...
|-> openmoko-sar
| |
| |-> packages
| | |
| | |-> images
| | | |
| | | |-> openmoko-sar-devel-image.bb
| | | |-> openmoko-sar-image.bb

For a first test we will put our own image recipes into this tree, and create the new recipes based on the image recipes from <code>$OPENMOKODIR/oe/packages/images/</code>. Simply copy the existing recipes, change their name, modify the <code>require</code> statement in (the now new) <code>openmoko-sar-devel-image.bb</code>. At a later time we plan to put this structure into a version control system.