https://www.openembedded.org/w/api.php?action=feedcontributions&feedformat=atom&user=JlamorieOpenembedded.org - User contributions [en]2026-06-01T17:34:39ZUser contributionsMediaWiki 1.39.10https://www.openembedded.org/w/index.php?title=User:Jlamorie&diff=859User:Jlamorie2008-12-10T17:40:54Z<p>Jlamorie: </p>
<hr />
<div>== OpenEmbedded Recipes ==<br />
<br />
This is my log of trying to understand what each element of a .bb file is.<br />
<br />
== linux recipes ==<br />
<br />
=== Definitions ===<br />
<br />
<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?<br />
<br />
<code>DESCRIPTION</code> - Description of package to be built. I assume this shows up in the ipkg meta data.<br />
<br />
<code>LICENSE</code> - GPL or other. How is this used?<br />
<br />
<code>DEPENDS</code> - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.<br />
<br />
<code>PR</code> - How is this used?<br />
<br />
<code>DEFAULT_PREFERENCE</code> - How is this used?<br />
<br />
<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?<br />
<br />
<code>SRC_URI</code> - Some documentation available at berlios.de[http://bitbake.berlios.de/manual/ch03.html].<br />
<br />
<code>S</code> - Source directory, I think.<br />
<br />
<code>FILES_kernel-image</code> - The complete path of the final kernel-image in the destination filesystem.<br />
<br />
<code>OS</code> - How is this used?<br />
<br />
<code>ARCH</code> - How is this used?<br />
<br />
<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.<br />
* vmlinux<br />
* image<br />
* uImage<br />
* bzImage<br />
* zImage<br />
* zImage.flash<br />
<br />
<code>KERNEL_OUTPUT</code> - Where in the kernel build tree is the final image.<br />
<br />
<code>COMPATIBLE_HOST</code> - How is this used?<br />
<br />
=== Functions ===<br />
<br />
<code>do_configure()</code> - Runs before X and after Y. In the case of building a kernel</div>Jlamoriehttps://www.openembedded.org/w/index.php?title=User:Jlamorie&diff=858User:Jlamorie2008-12-10T17:23:01Z<p>Jlamorie: /* Definitions */</p>
<hr />
<div>==== OpenEmbedded Recipes ====<br />
<br />
This is my log of trying to understand what each element of a .bb file is.<br />
<br />
=== linux recipes ===<br />
<br />
== Definitions ==<br />
<br />
<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?<br />
<br />
<code>DESCRIPTION</code> - Description of package to be built. I assume this shows up in the ipkg meta data.<br />
<br />
<code>LICENSE</code> - GPL or other. How is this used?<br />
<br />
<code>DEPENDS</code> - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.<br />
<br />
<code>PR</code> - How is this used?<br />
<br />
<code>DEFAULT_PREFERENCE</code> - How is this used?<br />
<br />
<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?<br />
<br />
<code>SRC_URI</code> - Some documentation available at berlios.de[http://bitbake.berlios.de/manual/ch03.html].<br />
<br />
<code>S</code> - Source directory, I think.<br />
<br />
<code>FILES_kernel-image</code> - The complete path of the final kernel-image in the destination filesystem.<br />
<br />
<code>OS</code> - How is this used?<br />
<br />
<code>ARCH</code> - How is this used?<br />
<br />
<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.<br />
* vmlinux<br />
* image<br />
* uImage<br />
* bzImage<br />
* zImage<br />
* zImage.flash<br />
<br />
<code>KERNEL_OUTPUT</code> - Where in the kernel build tree is the final image.</div>Jlamoriehttps://www.openembedded.org/w/index.php?title=User:Jlamorie&diff=857User:Jlamorie2008-12-10T17:21:16Z<p>Jlamorie: /* Definitions */</p>
<hr />
<div>==== OpenEmbedded Recipes ====<br />
<br />
This is my log of trying to understand what each element of a .bb file is.<br />
<br />
=== linux recipes ===<br />
<br />
== Definitions ==<br />
<br />
<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?<br />
<br />
<code>DESCRIPTION</code> - Description of package to be built. I assume this shows up in the ipkg meta data.<br />
<br />
<code>LICENSE</code> - GPL or other. How is this used?<br />
<br />
<code>DEPENDS</code> - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.<br />
<br />
<code>PR</code> - How is this used?<br />
<br />
<code>DEFAULT_PREFERENCE</code> - How is this used?<br />
<br />
<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?<br />
<br />
<code>SRC_URI</code> - Some documentation available at berlios.de[http://bitbake.berlios.de/manual/ch03.html].<br />
<br />
<code>S</code> - Source directory, I think.<br />
<br />
<code>FILES_kernel-image</code> - The complete path of the final kernel-image in the destination filesystem.<br />
<br />
<code>OS</code> - How is this used?<br />
<br />
<code>ARCH</code> - How is this used?<br />
<br />
<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.<br />
* vmlinux<br />
* image<br />
* uImage<br />
* bzImage<br />
* zImage<br />
* zImage.flash</div>Jlamoriehttps://www.openembedded.org/w/index.php?title=User:Jlamorie&diff=856User:Jlamorie2008-12-10T17:15:48Z<p>Jlamorie: /* Definitions */</p>
<hr />
<div>==== OpenEmbedded Recipes ====<br />
<br />
This is my log of trying to understand what each element of a .bb file is.<br />
<br />
=== linux recipes ===<br />
<br />
== Definitions ==<br />
<br />
<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?<br />
<br />
<code>DESCRIPTION</code> - Description of package to be built. I assume this shows up in the ipkg meta data.<br />
<br />
<code>LICENSE</code> - GPL or other. How is this used?<br />
<br />
<code>DEPENDS</code> - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.<br />
<br />
<code>PR</code> - How is this used?<br />
<br />
<code>DEFAULT_PREFERENCE</code> - How is this used?<br />
<br />
<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?<br />
<br />
<code>SRC_URI</code> - Some documentation available at [http://bitbake.berlios.de/manual/ch03.html|http://bitbake.berlios.de/manual/ch03.html].</div>Jlamoriehttps://www.openembedded.org/w/index.php?title=User:Jlamorie&diff=855User:Jlamorie2008-12-10T17:15:15Z<p>Jlamorie: /* Definitions */</p>
<hr />
<div>==== OpenEmbedded Recipes ====<br />
<br />
This is my log of trying to understand what each element of a .bb file is.<br />
<br />
=== linux recipes ===<br />
<br />
== Definitions ==<br />
<br />
<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?<br />
<br />
<code>DESCRIPTION</code> - Description of package to be built. I assume this shows up in the ipkg meta data.<br />
<br />
<code>LICENSE</code> - GPL or other. How is this used?<br />
<br />
<code>DEPENDS</code> - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.<br />
<br />
<code>PR</code> - How is this used?<br />
<br />
<code>DEFAULT_PREFERENCE</code> - How is this used?<br />
<br />
<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?<br />
<br />
<code>SRC_URI</code> - Some documentation available at [http://bitbake.berlios.de/manual/ch03.html].</div>Jlamoriehttps://www.openembedded.org/w/index.php?title=User:Jlamorie&diff=854User:Jlamorie2008-12-10T17:11:35Z<p>Jlamorie: /* Definitions */</p>
<hr />
<div>==== OpenEmbedded Recipes ====<br />
<br />
This is my log of trying to understand what each element of a .bb file is.<br />
<br />
=== linux recipes ===<br />
<br />
== Definitions ==<br />
<br />
<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?<br />
<br />
<code>DESCRIPTION</code> - Description of package to be built. I assume this shows up in the ipkg meta data.<br />
<br />
<code>LICENSE</code> - GPL or other. How is this used?<br />
<br />
<code>DEPENDS</code> - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.<br />
<br />
<code>PR</code> - How is this used?<br />
<br />
<code>DEFAULT_PREFERENCE</code> - How is this used?</div>Jlamoriehttps://www.openembedded.org/w/index.php?title=User:Jlamorie&diff=853User:Jlamorie2008-12-10T17:10:47Z<p>Jlamorie: /* Definitions */</p>
<hr />
<div>==== OpenEmbedded Recipes ====<br />
<br />
This is my log of trying to understand what each element of a .bb file is.<br />
<br />
=== linux recipes ===<br />
<br />
== Definitions ==<br />
<br />
<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?<br />
<br />
'DESCRIPTION' - Description of package to be built. I assume this shows up in the ipkg meta data.<br />
<br />
'LICENSE' - GPL or other. How is this used?<br />
<br />
'DEPENDS' - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.<br />
<br />
'PR - How is this used?<br />
<br />
'DEFAULT_PREFERENCE' - How is this used?</div>Jlamoriehttps://www.openembedded.org/w/index.php?title=User:Jlamorie&diff=852User:Jlamorie2008-12-10T17:08:45Z<p>Jlamorie: Package Recipe Description</p>
<hr />
<div>==== OpenEmbedded Recipes ====<br />
<br />
This is my log of trying to understand what each element of a .bb file is.<br />
<br />
=== linux recipes ===<br />
<br />
== Definitions ==<br />
<br />
'SECTION' - Top level package section. base, kernel, libs, x11, x11/utils. This appears to be similar to a bbclass. How is this used?<br />
<br />
'DESCRIPTION' - Description of package to be built. I assume this shows up in the ipkg meta data.<br />
<br />
'LICENSE' - GPL or other. How is this used?<br />
<br />
'DEPENDS' - This package cannot be built/recipe not baked until the packages/recipes listed in DEPENDS have been built/baked.<br />
<br />
'PR - How is this used?<br />
<br />
'DEFAULT_PREFERENCE' - How is this used?</div>Jlamorie