Difference between revisions of "Kernel Building"

From Openembedded.org
Jump to: navigation, search
(Kernel configuration)
(Default Build)
Line 5: Line 5:
  
 
After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.
 
After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.
 +
 +
 +
== Kernel image type ==
 +
 +
What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>. For example, build image for u-boot
 +
  KERNEL_IMAGETYPE = "uImage"
  
 
== Kernel configuration ==
 
== Kernel configuration ==

Revision as of 14:42, 20 October 2010

Contents

Default Build

For a default build, just run:

 bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin.


Kernel image type

What kind of kernel image to build is controlled by the variable KERNEL_IMAGETYPE. For example, build image for u-boot

 KERNEL_IMAGETYPE = "uImage"

Kernel configuration

The default .config file used is placed in ???/defconfig.

Custom config

If you need to customize the kernel configuration, run the menuconfig task by:

 bitbake -c menuconfig virtual/kernel

Note: by default this command requires you to run in X Windows.

After that, you can compile the kernel by:

 bitbake -f -c compile virtual/kernel
Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox