User:Jlamorie: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
Line 32: Line 32:


<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.
<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
* vmlinux
  * image
* image
  * uImage
* uImage
  * bzImage
* bzImage
  * zImage
* zImage
  * zImage.flash
* zImage.flash
 
<code>KERNEL_OUTPUT</code> - Where in the kernel build tree is the final image.

Revision as of 17:23, 10 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[1].

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.