From cbf8516c083ebf7fc4b1a3018702b78989f64f1f Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 8 Aug 2016 09:38:00 -0700 Subject: 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 Signed-off-by: Richard Purdie --- .../bitbake-user-manual-metadata.xml | 28 ++++++++++++++++++++++ 1 file changed, 28 insertions(+) (limited to 'bitbake') 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 @@ KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc" + Setting a Variable for a Single Task: + BitBake supports setting a variable just for the + duration of a single task. + Here is an example: + + FOO_task-configure = "val 1" + FOO_task-compile = "val 2" + + In the previous example, FOO + has the value "val 1" while the + do_configure task is executed, + and the value "val 2" while the + do_compile task is executed. + + + Internally, this is implemented by prepending + the task (e.g. "task-compile:") to the value of + OVERRIDES + for the local datastore of the do_compile + task. + + You can also use this syntax with other combinations + (e.g. "_prepend") as shown in the + following example: + + EXTRA_OEMAKE_prepend_task-compile = "${PARALLEL_MAKE} " + + -- cgit 1.2.3-korg