Useful targets: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
(Undo revision 3321 by Yjytalamago (Talk))
No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Other ==
Useful targets for bitbake (bitbake <targetname>)


=== helloworld ===
= core-image-minimal =
Builds a static executable that prints hello world, then loops infinitely.
Builds a minimal image for your target with basic system functionality, booting to a shell.


=== world ===
= 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.


=== 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 the opkg 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 =
Builds the appropriate kernel for your device.
Builds the appropriate kernel for your device.


[[Category:User]]
[[Category:User]]

Latest revision as of 15:19, 7 November 2012

Useful targets for bitbake (bitbake <targetname>)

core-image-minimal

Builds a minimal image for your target with basic system functionality, booting to a shell.

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.