User:Jlamorie - Revision history

Laibsch: /* Definitions */

2008-12-23T15:21:06Z

Definitions

← Older revision		Revision as of 15:21, 23 December 2008
Line 21:		Line 21:
	<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>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 ~~documentation available at berlios.de~~[http://bitbake.berlios.de/manual/ch03.html].		<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>S</code> - Source directory, I think.

Jlamorie at 17:40, 10 December 2008

2008-12-10T17:40:54Z

← Older revision		Revision as of 17:40, 10 December 2008
Line 1:		Line 1:
	==== OpenEmbedded Recipes ====		== 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 ===		== 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?
Line 40:		Line 40:

	<code>KERNEL_OUTPUT</code> - Where in the kernel build tree is the final image.		<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

Jlamorie: /* Definitions */

2008-12-10T17:23:01Z

Definitions

← Older revision		Revision as of 17:23, 10 December 2008
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.

Jlamorie: /* Definitions */

2008-12-10T17:21:16Z

Definitions

← Older revision		Revision as of 17:21, 10 December 2008
Line 21:		Line 21:
	<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>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 documentation available at [http://bitbake.berlios.de/manual/ch03.html~~\|http:~~//~~bitbake~~.~~berlios.de~~/~~manual~~/~~ch03~~.~~html]~~.		<code>SRC_URI</code> - Some documentation available at berlios.de[http://bitbake.berlios.de/manual/ch03.html].

			<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

Jlamorie: /* Definitions */

2008-12-10T17:15:48Z

Definitions

← Older revision		Revision as of 17:15, 10 December 2008
Line 21:		Line 21:
	<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>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 documentation available at [http://bitbake.berlios.de/manual/ch03.html].		<code>SRC_URI</code> - Some documentation available at [http://bitbake.berlios.de/manual/ch03.html\|http://bitbake.berlios.de/manual/ch03.html].

Jlamorie: /* Definitions */

2008-12-10T17:15:15Z

Definitions

← Older revision		Revision as of 17:15, 10 December 2008
Line 18:		Line 18:

	<code>DEFAULT_PREFERENCE</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 documentation available at [http://bitbake.berlios.de/manual/ch03.html].

Jlamorie: /* Definitions */

2008-12-10T17:11:35Z

Definitions

← Older revision		Revision as of 17:11, 10 December 2008
Line 9:		Line 9:
	<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?

	'DESCRIPTION' - Description of package to be built. I assume this shows up in the ipkg meta data.		<code>DESCRIPTION</code> - Description of package to be built. I assume this shows up in the ipkg meta data.

	'LICENSE' - GPL or other. How is this used?		<code>LICENSE</code> - 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.		<code>DEPENDS</code> - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.

	'PR - How is this used?		<code>PR</code> - How is this used?

	'DEFAULT_PREFERENCE' - How is this used?		<code>DEFAULT_PREFERENCE</code> - How is this used?

Jlamorie: /* Definitions */

2008-12-10T17:10:47Z

Definitions

← Older revision		Revision as of 17:10, 10 December 2008
Line 7:		Line 7:
	== Definitions ==		== Definitions ==

	'SECTION' - 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?

	'DESCRIPTION' - Description of package to be built. I assume this shows up in the ipkg meta data.		'DESCRIPTION' - Description of package to be built. I assume this shows up in the ipkg meta data.

Jlamorie: Package Recipe Description

2008-12-10T17:08:45Z

Package Recipe Description

New page

==== 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?