mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-07-17 04:07:06 +00:00
Code Issues Projects Releases Wiki Activity

Rename poky-image-* -> core-image-* and task-poky-* -> task-core-*

Browse Source 
(From yocto-docs rev: 0feb6b8f9621087ba5fd77d3c8f3e23132c97187)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Richard Purdie
2011-04-20 17:25:58 +01:00
parent b3d84fb35a
commit e9b17e3fa7
7 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/poky-ref-manual/ref-bitbake.xml
+3 -3
View File
@@ -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:
<literallayout class='monospaced'>
$ bitbake poky-image-sato
$ bitbake core-image-sato
</literallayout>
</para>
@@ -111,11 +111,11 @@
<para>
Once all the <filename>.bb</filename> 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 <filename>task-base.bb</filename>,
In the case of "core-image-sato", it would lead to <filename>task-base.bb</filename>,
which in turn leads to packages like <application>Contacts</application>,
<application>Dates</application> and <application>BusyBox</application>.
These packages in turn depend on glibc and the toolchain.