Useful targets: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
(Elaborated on the description of the GPE build target.)
Line 72: Line 72:


=== package-index ===
=== 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.
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.


=== virtual/kernel ===
=== virtual/kernel ===

Revision as of 11:20, 25 March 2009

Overview

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.

Images

helloworld-image

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).

bootstrap-image

Build image contains task-base packages.

console-image

Build an image without the X11, gtk+, or qt windowing libraries.

x11-image

Builds an image with X11

beagleboard-demo-image

Builds the Angstrom distribution like Koen proposed.

opie-image

Build image based on the Open Palmtop Integrated Environment (OPIE). OPIE is a completely Open Source based graphical user environment and suite of applications for small form-factor devices, such as PDAs, running Linux.

opie-kdepim-image

Build image based on the OPIE and full featured KDE-based PIM (pi-sync, ko/pi, ka/pi, etc).

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.

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

Build a GPE Palmtop Environment based kernel and rootfs. The GPE provides a user interface environment for palmtop/handheld computers running the GNU/Linux or any other UNIX-like operating system.

Tasks

task-base

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.

task-dvb

meta-package for DVB application (DVB = Digital Video Broadcasting).

task-python-everything

all of python.

task-native-sdk

mate-package for native (on-device) SDK

Meta

The directory packages/meta contains most of these "meta" targets that build multiple packages but some of the more useful ones are detailed below:

meta-opie

Build all OPIE related packages and some more for OPIE based usage.

meta-gpe

Basic packages to go with gpe-image.

Other

helloworld

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.

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 the opkg command line tools.

virtual/kernel

Builds the appropriate kernel for your device.