Creating a new Layer - Revision history

PaulEggleton: Update for removal of qt4 bbappends in meta-oe

2013-04-19T11:03:51Z

Update for removal of qt4 bbappends in meta-oe

← Older revision		Revision as of 11:03, 19 April 2013
Line 19:		Line 19:

	* Avoid "overlaying" entire recipes from other layers in your configuration (i.e. copying the entire recipe into your layer and modifying it). Use .bbappend files to override the parts of the recipe you need to modify.		* Avoid "overlaying" entire recipes from other layers in your configuration (i.e. copying the entire recipe into your layer and modifying it). Use .bbappend files to override the parts of the recipe you need to modify.
	* Avoid duplicating include files - use .bbappends for each recipe that uses the inc file, or if you're introducing a new recipe that requires it, use the full path to refer to the original (e.g. require recipes-core/somepackage/somefile.inc instead of require somefile.inc). If you're finding you have to overlay the inc file it may indicate a deficiency in the inc file in the layer it originally belongs to, which should be addressed instead. An example here would be the way Qt 4 database support plugins are configured - OE-core doesn't have MySQL or PostgreSQL, however meta-oe does, so ~~meta-oe uses~~ .bbappends to modify a variable QT_SQL_DRIVER_FLAGS to enable the appropriate plugins. This variable was added to qt4.inc in OE-core specifically to ~~allow meta~~-~~oe to be able to control which plugins are built~~.		* Avoid duplicating include files - use .bbappends for each recipe that uses the inc file, or if you're introducing a new recipe that requires it, use the full path to refer to the original (e.g. require recipes-core/somepackage/somefile.inc instead of require somefile.inc). If you're finding you have to overlay the inc file it may indicate a deficiency in the inc file in the layer it originally belongs to, which should be addressed instead. An example here would be the way Qt 4 database support plugins are configured - OE-core doesn't have MySQL or PostgreSQL, however meta-oe does, so distro layers can use .bbappends for qt4-x11-free and/or qt4-embedded to modify a variable QT_SQL_DRIVER_FLAGS to enable the appropriate plugins. This variable was added to qt4.inc in OE-core specifically to make it easier to enable support for database engines not available in OE-Core.

PaulEggleton: Change link to layer index

2013-04-10T08:50:40Z

Change link to layer index

← Older revision		Revision as of 08:50, 10 April 2013
Line 1:		Line 1:
	== Before creating a new layer ==		== Before creating a new layer ==

	Check if someone has already created a layer containing the metadata you're looking for - the [~~[LayerIndex]~~] is ~~currently~~ the place where layers are tracked.		Check if someone has already created a layer containing the metadata you're looking for - the [http://layers.openembedded.org layer index] is the place where layers are tracked.

	== How to create a new layer ==		== How to create a new layer ==

PaulEggleton: Link to LayerIndex

2012-02-15T11:38:09Z

Link to LayerIndex

← Older revision		Revision as of 11:38, 15 February 2012
Line 1:		Line 1:
			== Before creating a new layer ==

			Check if someone has already created a layer containing the metadata you're looking for - the [[LayerIndex]] is currently the place where layers are tracked.

	== How to create a new layer ==		== How to create a new layer ==

PaulEggleton at 11:33, 15 February 2012

2012-02-15T11:33:00Z

← Older revision		Revision as of 11:33, 15 February 2012
Line 5:		Line 5:
	# Create a new directory (traditionally meta-<something>)		# Create a new directory (traditionally meta-<something>)
	# Create a conf/layer.conf. You can simply copy [http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/conf/layer.conf meta-oe's] one and just change "openembedded-layer" to something appropriate for your layer; you may also want to set the priority as appropriate.		# Create a conf/layer.conf. You can simply copy [http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/conf/layer.conf meta-oe's] one and just change "openembedded-layer" to something appropriate for your layer; you may also want to set the priority as appropriate.
	# ~~Create~~/~~copy~~ in the recipes you need ~~into~~ recipes-* subdirectories of the layer directory. If you are bringing recipes across from OE-Classic see [[Migrating metadata to OE-Core]].		# Depending on the type of layer, add the content:
			#* If the layer is adding support for a machine, add the machine configuration in conf/machine/
			#* If the layer is adding distro policy, add the distro configuration in conf/distro/
			#* If the layer introduces new recipes, put the recipes you need in recipes-* subdirectories of the layer directory. If you are bringing recipes across from OE-Classic see [[Migrating metadata to OE-Core]].

	== Best practices ==		== Best practices ==

PaulEggleton: Created page with "== How to create a new layer == Creating a layer is simple: # Create a new directory (traditionally meta-) # Create a conf/layer.conf. You can simply copy [http://cg..."

2012-02-15T11:29:55Z

Created page with "== How to create a new layer == Creating a layer is simple: # Create a new directory (traditionally meta-<something>) # Create a conf/layer.conf. You can simply copy [http://cg..."

New page

== How to create a new layer ==

Creating a layer is simple:

# Create a new directory (traditionally meta-<something>)
# Create a conf/layer.conf. You can simply copy [http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/conf/layer.conf meta-oe's] one and just change "openembedded-layer" to something appropriate for your layer; you may also want to set the priority as appropriate.
# Create/copy in the recipes you need into recipes-* subdirectories of the layer directory. If you are bringing recipes across from OE-Classic see [[Migrating metadata to OE-Core]].

== Best practices ==

To aid maintainability, the following recommendations are made for creating new layers:

* Avoid "overlaying" entire recipes from other layers in your configuration (i.e. copying the entire recipe into your layer and modifying it). Use .bbappend files to override the parts of the recipe you need to modify.
* Avoid duplicating include files - use .bbappends for each recipe that uses the inc file, or if you're introducing a new recipe that requires it, use the full path to refer to the original (e.g. require recipes-core/somepackage/somefile.inc instead of require somefile.inc). If you're finding you have to overlay the inc file it may indicate a deficiency in the inc file in the layer it originally belongs to, which should be addressed instead. An example here would be the way Qt 4 database support plugins are configured - OE-core doesn't have MySQL or PostgreSQL, however meta-oe does, so meta-oe uses .bbappends to modify a variable QT_SQL_DRIVER_FLAGS to enable the appropriate plugins. This variable was added to qt4.inc in OE-core specifically to allow meta-oe to be able to control which plugins are built.