|
|
(65 intermediate revisions by 19 users not shown) |
Line 1: |
Line 1: |
− | = Useful Targets =
| + | Useful targets for bitbake (bitbake <targetname>) |
| | | |
− | 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:
| + | = core-image-minimal = |
| + | Builds a minimal image for your target with basic system functionality, booting to a shell. |
| | | |
− | == helloworld == | + | = world = |
− | Builds a static executable that prints hello world, then loops infinitely.
| |
− | | |
− | == world ==
| |
| Build everything. This takes a long time, a lot of network bandwidth, and a lot of disc space. Can also break your toolchain. | | Build everything. This takes a long time, a lot of network bandwidth, and a lot of disc space. Can also break your toolchain. |
| | | |
− | == task-base == | + | = package-index = |
− | 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.
| + | 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 the opkg command line tools. |
| | | |
− | == helloworld-image == | + | = virtual/kernel = |
− | 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). | + | Builds the appropriate kernel for your device. |
− | | |
− | == bootstrap-image ==
| |
− | Build image contains task-base packages.
| |
− | | |
− | == opie-image ==
| |
− | Build image based on the OPIE.
| |
− | | |
− | == console-image ==
| |
− | Build an image without the X11, gtk+, or qt windowing libraries.
| |
− | | |
− | == opie-kdepim-image ==
| |
− | Build image based on the OPIE and full featured KDE-based PIM (pi-sync, ko/pi, ka/pi, etc).
| |
− | | |
− | == meta-opie ==
| |
− | Build all OPIE related packages and some more for OPIE based usage.
| |
− | | |
− | == pivotboot-image ==
| |
− | 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.
| |
− | | |
− | == task-dvb ==
| |
− | meta-package for DVB application (DVB = Digital Video Broadcasting).
| |
− | | |
− | == task-python-everything ==
| |
− | all of python.
| |
− | | |
− | == twin-image ==
| |
− | task-base plus a couple of editors nano and vim --- why two? and a mail reader mutt
| |
− | | |
− | == uml-image ==
| |
− | A root image for user-mode-linux. Includes task-base, and parts of opie I think.
| |
− | | |
− | == gpe-image ==
| |
− | GPE-based kernel and rootfs.
| |
− | | |
− | == meta-gpe ==
| |
− | Basic packages to go with gpe-image.
| |
− | | |
− | == package-index ==
| |
− | 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.
| |
| | | |
− | == virtual/kernel ==
| + | [[Category:User]] |
− | Builds the appropriate kernel for your device.
| |
Builds a minimal image for your target with basic system functionality, booting to a shell.
Build everything. This takes a long time, a lot of network bandwidth, and a lot of disc space. Can also break your toolchain.
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 the opkg command line tools.
Builds the appropriate kernel for your device.