- 1 Useful Targets
- 1.1 helloworld
- 1.2 world
- 1.3 task-base
- 1.4 helloworld-image
- 1.5 bootstrap-image
- 1.6 console-image
- 1.7 opie-image
- 1.8 opie-kdepim-image
- 1.9 meta-opie
- 1.10 pivotboot-image
- 1.11 task-dvb
- 1.12 task-python-everything
- 1.13 twin-image
- 1.14 uml-image
- 1.15 gpe-image
- 1.16 meta-gpe
- 1.17 package-index
- 1.18 virtual/kernel
Bitbake can build individual packages such as "bitbake nano" to build the single package nano, but it's often more useful to build a set of things and say compile them into an image. The directory packages/meta contains most of these "meta" targets that build multiple packages but some of the more useful ones are detailed below:
Builds a static executable that prints hello world, then loops infinitely.
Build everything. This takes a long time, a lot of network bandwidth, and a lot of disc space. Can also break your toolchain.
Build a kernel and core packages for a basic installation. You won't be able to do much more than ssh to the machine if this is all that's installed.
Builds an image, that if used as a root filesystem, will start a static executable that prints hello world, then loops infinitely. Can be used to test the Linux boot procedure into user space (init).
Build image contains task-base packages.
Build an image without the X11, gtk+, or qt windowing libraries.
Build image based on the OPIE.
Build image based on the OPIE and full featured KDE-based PIM (pi-sync, ko/pi, ka/pi, etc).
Build all OPIE related packages and some more for OPIE based usage.
Build image that is necessary to flash a Sharp SL C3000, Zaurus. It pivots after booting from the NAND and finalizes the install to the HD during the first boot.
meta-package for DVB application (DVB = Digital Video Broadcasting).
all of python.
task-base plus a couple of editors nano and vim --- why two? and a mail reader mutt
A root image for user-mode-linux. Includes task-base, and parts of opie I think.
GPE-based kernel and rootfs.
Basic packages to go with gpe-image.
Target to update the "feed" files (Package*) to reflect the current set of .ipk's that exist in the deploy directory. Commonly used after building some packages individually to update the feed and allow them to be installed via a package manager or thie ipkg command line tools.
Builds the appropriate kernel for your device.