Writes output files that are to be deployed to
${
DEPLOY_DIR_IMAGE
}
.
The task runs with the current working directory set to
${
B
}
.
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}
.
${DEPLOY_DIR_IMAGE}
, as this causes
the sstate mechanism to malfunction.
The do_deploy
task is not added as a task
by default and consequently needs to be added manually.
If you want the task to run after
do_compile
,
you can add it by doing the following:
addtask deploy after do_compile
Adding do_deploy
after other tasks works the
same way.
before do_build
to the addtask
command (though it is
harmless), because the
base
class contains the following:
do_build[recrdeptask] += "do_deploy"See the "Dependencies" section in the BitBake User Manual for more information.
If the do_deploy
task re-executes, any
previous output is removed (i.e. "cleaned").