From e9b17e3fa7f15740d8e5cfdfe19c0565a74c0d20 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 20 Apr 2011 17:25:58 +0100 Subject: Rename poky-image-* -> core-image-* and task-poky-* -> task-core-* (From yocto-docs rev: 0feb6b8f9621087ba5fd77d3c8f3e23132c97187) Signed-off-by: Richard Purdie --- documentation/poky-ref-manual/ref-bitbake.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'documentation/poky-ref-manual/ref-bitbake.xml') diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml index 75b3bf5e54..df8432c91b 100644 --- a/documentation/poky-ref-manual/ref-bitbake.xml +++ b/documentation/poky-ref-manual/ref-bitbake.xml @@ -9,7 +9,7 @@ BitBake is a program written in Python that interprets the metadata that makes up Poky. At some point, people wonder what actually happens when you enter: - $ bitbake poky-image-sato + $ bitbake core-image-sato @@ -111,11 +111,11 @@ Once all the .bb files have been - parsed, BitBake starts to build the target (poky-image-sato in the previous section's + parsed, BitBake starts to build the target (core-image-sato in the previous section's example) and looks for providers of that target. Once a provider is selected, BitBake resolves all the dependencies for the target. - In the case of "poky-image-sato", it would lead to task-base.bb, + In the case of "core-image-sato", it would lead to task-base.bb, which in turn leads to packages like Contacts, Dates and BusyBox. These packages in turn depend on glibc and the toolchain. -- cgit v1.2.3-54-g00ecf