From 30929cf03738d5a871e410678e332ee3bdc51771 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 18 Jul 2016 13:06:59 -0700 Subject: ref-manual: Updated the do_deploy task reference section. Fixes [YOCTO #9970] Added more detail to the do_deploy task. (From yocto-docs rev: 1b2daf814011dbc3c5987313442e95e18e83e180) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-tasks.xml | 55 ++++++++++++++++++++++++++++------ 1 file changed, 46 insertions(+), 9 deletions(-) (limited to 'documentation/ref-manual/ref-tasks.xml') diff --git a/documentation/ref-manual/ref-tasks.xml b/documentation/ref-manual/ref-tasks.xml index 15043c4ea7..34d0bdb7e7 100644 --- a/documentation/ref-manual/ref-tasks.xml +++ b/documentation/ref-manual/ref-tasks.xml @@ -130,18 +130,55 @@ <filename>do_deploy</filename> - Writes output files that are to be deployed to the deploy - directory, which is defined by the - DEPLOYDIR - variable. + Writes output files that are to be deployed to + ${DEPLOY_DIR_IMAGE}. + The task runs with the current working directory set to + ${B}. - The do_deploy task is a - shared state (sstate) task, which means that the task can - be accelerated through sstate use. - Realize also that if the task is re-executed, any previous output - is removed (i.e. "cleaned"). + Recipes implementing this task should inherit the + deploy + class and should write the output to + ${DEPLOYDIR}, + which is not to be confused with + ${DEPLOY_DIR}. + The deploy class sets up + do_deploy as a shared state (sstate) task that + can be accelerated through sstate use. + The sstate mechanism takes care of copying the output from + ${DEPLOYDIR} to + ${DEPLOY_DIR_IMAGE}. + + Caution + Do not write the output directly to + ${DEPLOY_DIR_IMAGE}, as this causes + the sstate mechanism to malfunction. + + + + + The do_deploy task is not added as a task by + default and needs to be added manually. + You can add this task using the following: + + addtask deploy after do_compile + + If the do_deploy should run some time after + the do_compile, the + base.bbclass has the following to ensure that + all do_deploy tasks run by default. + See the + "Dependencies" + section in the BitBake User Manual for more information. + + do_build[recrdeptask] += "do_deploy" + + + + + If the do_deploy task re-executes, any + previous output is removed (i.e. "cleaned"). -- cgit v1.2.3-54-g00ecf