diff options
| author | Scott Rifenbark <srifenbark@gmail.com> | 2016-08-08 09:38:00 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-08-17 10:22:59 +0100 |
| commit | cbf8516c083ebf7fc4b1a3018702b78989f64f1f (patch) | |
| tree | d1b2ee3af14e69d3c8be7ce4742a71a847b32ec6 /bitbake/doc | |
| parent | 277a5a969fd7a35c8e5d112861ba6a815c0af0ec (diff) | |
| download | poky-cbf8516c083ebf7fc4b1a3018702b78989f64f1f.tar.gz | |
bitbake: bitbake-user-manual: Added setting variable for a single task
Fixes [YOCTO #10095]
I added a third case to the "Conditional Metadata" section to
describe setting a variable for a single task.
(Bitbake rev: 24d648ce62b35f7d2b23fde732703c060579a0d2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/doc')
| -rw-r--r-- | bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml index 4fa51c446d..3d9234cba6 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | |||
| @@ -557,6 +557,34 @@ | |||
| 557 | KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc" | 557 | KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc" |
| 558 | </literallayout> | 558 | </literallayout> |
| 559 | </para></listitem> | 559 | </para></listitem> |
| 560 | <listitem><para><emphasis>Setting a Variable for a Single Task:</emphasis> | ||
| 561 | BitBake supports setting a variable just for the | ||
| 562 | duration of a single task. | ||
| 563 | Here is an example: | ||
| 564 | <literallayout class='monospaced'> | ||
| 565 | FOO_task-configure = "val 1" | ||
| 566 | FOO_task-compile = "val 2" | ||
| 567 | </literallayout> | ||
| 568 | In the previous example, <filename>FOO</filename> | ||
| 569 | has the value "val 1" while the | ||
| 570 | <filename>do_configure</filename> task is executed, | ||
| 571 | and the value "val 2" while the | ||
| 572 | <filename>do_compile</filename> task is executed. | ||
| 573 | </para> | ||
| 574 | |||
| 575 | <para>Internally, this is implemented by prepending | ||
| 576 | the task (e.g. "task-compile:") to the value of | ||
| 577 | <link linkend='var-OVERRIDES'><filename>OVERRIDES</filename></link> | ||
| 578 | for the local datastore of the <filename>do_compile</filename> | ||
| 579 | task.</para> | ||
| 580 | |||
| 581 | <para>You can also use this syntax with other combinations | ||
| 582 | (e.g. "<filename>_prepend</filename>") as shown in the | ||
| 583 | following example: | ||
| 584 | <literallayout class='monospaced'> | ||
| 585 | EXTRA_OEMAKE_prepend_task-compile = "${PARALLEL_MAKE} " | ||
| 586 | </literallayout> | ||
| 587 | </para></listitem> | ||
| 560 | </itemizedlist> | 588 | </itemizedlist> |
| 561 | </para> | 589 | </para> |
| 562 | </section> | 590 | </section> |
