Kernel Building: Difference between revisions
Jump to navigation
Jump to search
Michaelfung (talk | contribs) |
Michaelfung (talk | contribs) |
||
| Line 11: | Line 11: | ||
What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>. For example, build image for u-boot | 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_IMAGETYPE = "uImage" | ||
== Select kernel version == | |||
To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35. | |||
== Kernel configuration == | == Kernel configuration == | ||
Revision as of 14:54, 20 October 2010
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"
Select kernel version
To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.
Kernel configuration
The default .config file used is placed in ???/defconfig.
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