User:Jlamorie: Difference between revisions
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== OpenEmbedded Recipes == | |||
This is my log of trying to understand what each element of a .bb file is. | This is my log of trying to understand what each element of a .bb file is. | ||
== linux recipes == | |||
== Definitions == | === Definitions === | ||
<code>SECTION</code> - Top level package section. base, kernel, libs, x11, x11/utils. This appears to be similar to a bbclass. How is this used? | <code>SECTION</code> - Top level package section. base, kernel, libs, x11, x11/utils. This appears to be similar to a bbclass. How is this used? | ||
<code>DESCRIPTION</code> - Description of package to be built. I assume this shows up in the ipkg meta data. | |||
<code>LICENSE</code> - GPL or other. How is this used? | |||
<code>DEPENDS</code> - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked. | |||
<code>PR</code> - How is this used? | |||
<code>DEFAULT_PREFERENCE</code> - How is this used? | |||
<code>COMPATIBLE_MACHINE</code> - A machine as described in local.conf and with an appropriate config file in OE/conf/machine. How is this used? | |||
<code>SRC_URI</code> - Some [http://bitbake.berlios.de/manual/ch03.html documentation available at berlios.de]. | |||
<code>S</code> - Source directory, I think. | |||
<code>FILES_kernel-image</code> - The complete path of the final kernel-image in the destination filesystem. | |||
<code>OS</code> - How is this used? | |||
<code>ARCH</code> - How is this used? | |||
<code>KERNEL_IMAGETYPE</code> - Filename of the image to be built. The exact name is dependent on the architecture. Could be one of the following. | |||
* vmlinux | |||
* image | |||
* uImage | |||
* bzImage | |||
* zImage | |||
* zImage.flash | |||
<code>KERNEL_OUTPUT</code> - Where in the kernel build tree is the final image. | |||
<code>COMPATIBLE_HOST</code> - How is this used? | |||
=== Functions === | |||
<code>do_configure()</code> - Runs before X and after Y. In the case of building a kernel | |||
Latest revision as of 15:21, 23 December 2008
OpenEmbedded Recipes
This is my log of trying to understand what each element of a .bb file is.
linux recipes
Definitions
SECTION - Top level package section. base, kernel, libs, x11, x11/utils. This appears to be similar to a bbclass. How is this used?
DESCRIPTION - Description of package to be built. I assume this shows up in the ipkg meta data.
LICENSE - GPL or other. How is this used?
DEPENDS - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.
PR - How is this used?
DEFAULT_PREFERENCE - How is this used?
COMPATIBLE_MACHINE - A machine as described in local.conf and with an appropriate config file in OE/conf/machine. How is this used?
SRC_URI - Some documentation available at berlios.de.
S - Source directory, I think.
FILES_kernel-image - The complete path of the final kernel-image in the destination filesystem.
OS - How is this used?
ARCH - How is this used?
KERNEL_IMAGETYPE - Filename of the image to be built. The exact name is dependent on the architecture. Could be one of the following.
- vmlinux
- image
- uImage
- bzImage
- zImage
- zImage.flash
KERNEL_OUTPUT - Where in the kernel build tree is the final image.
COMPATIBLE_HOST - How is this used?
Functions
do_configure() - Runs before X and after Y. In the case of building a kernel