Kernel Building: Difference between revisions
Jump to navigation
Jump to search
Michaelfung (talk | contribs) |
Michaelfung (talk | contribs) (→Build) |
||
| Line 1: | Line 1: | ||
== Build == | == Build == | ||
For | For a default build, just run: | ||
bitbake virtual/kernel | bitbake virtual/kernel | ||
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 configuration == | |||
The default .config file used is placed in ???. | |||
== Custom config == | == Custom config == | ||
Revision as of 14:24, 20 October 2010
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 configuration
The default .config file used is placed in ???.
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.