diff options
Diffstat (limited to 'bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml')
-rw-r--r-- | bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml | 31 |
1 files changed, 30 insertions, 1 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml index 8b6e0b442f..571424b99f 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml | |||
@@ -7,7 +7,8 @@ | |||
7 | <para> | 7 | <para> |
8 | The primary purpose for running BitBake is to produce some kind | 8 | The primary purpose for running BitBake is to produce some kind |
9 | of output such as a single installable package, a kernel, a software | 9 | of output such as a single installable package, a kernel, a software |
10 | development kit, or even a full, board-specific bootable Linux image. | 10 | development kit, or even a full, board-specific bootable Linux image, |
11 | complete with bootloader, kernel, and root filesystem. | ||
11 | Of course, you can execute the <filename>bitbake</filename> | 12 | Of course, you can execute the <filename>bitbake</filename> |
12 | command with options that cause it to execute single tasks, | 13 | command with options that cause it to execute single tasks, |
13 | compile single recipe files, capture or clear data, or simply | 14 | compile single recipe files, capture or clear data, or simply |
@@ -45,6 +46,11 @@ | |||
45 | build host with hyper-threading will most likely show eight processors, | 46 | build host with hyper-threading will most likely show eight processors, |
46 | which is the value you would then assign to that variable. | 47 | which is the value you would then assign to that variable. |
47 | </para> | 48 | </para> |
49 | |||
50 | <para> | ||
51 | A possibly simpler solution is that some Linux distributions | ||
52 | (e.g. Debian and Ubuntu) provide the <filename>ncpus</filename> command. | ||
53 | </para> | ||
48 | </note> | 54 | </note> |
49 | </para> | 55 | </para> |
50 | 56 | ||
@@ -464,6 +470,29 @@ | |||
464 | PREFERRED_VERSION_a = "1.1" | 470 | PREFERRED_VERSION_a = "1.1" |
465 | </literallayout> | 471 | </literallayout> |
466 | </para> | 472 | </para> |
473 | |||
474 | <note> | ||
475 | <para> | ||
476 | It is common for a recipe to provide two versions -- a stable, | ||
477 | numbered (and preferred) version, and a version that is | ||
478 | automatically checked out from a source code repository that | ||
479 | is considered more "bleeding edge" but can be selected only | ||
480 | explicitly. | ||
481 | </para> | ||
482 | |||
483 | <para> | ||
484 | For example, in the OpenEmbedded codebase, there is a standard, | ||
485 | versioned recipe file for BusyBox, | ||
486 | <filename>busybox_1.22.1.bb</filename>, | ||
487 | but there is also a Git-based version, | ||
488 | <filename>busybox_git.bb</filename>, which explicitly contains the line | ||
489 | <literallayout class='monospaced'> | ||
490 | DEFAULT_PREFERENCE = "-1" | ||
491 | </literallayout> | ||
492 | to ensure that the numbered, stable version is always preferred | ||
493 | unless the developer selects otherwise. | ||
494 | </para> | ||
495 | </note> | ||
467 | </section> | 496 | </section> |
468 | 497 | ||
469 | <section id='bb-bitbake-dependencies'> | 498 | <section id='bb-bitbake-dependencies'> |