480bf037ae
When originally developed, it was thought a task may have more than one associated sstate archive. The way the code has grown that idea is now not possible or needed. We can therefore assume one sstate archive per task and drop the crazy name mapping code. Simpler is better in this case. The downside is that various sstate archives will change name so this forces a cache rebuild. Given the other sstate changes going in at this time, this isn't really a bad thing as things would rebuild anyway. (From OE-Core rev: 5afe86a6854b21692fd97c5fc7fab50dbc068acb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
11 lines
285 B
Text
11 lines
285 B
Text
DEPLOYDIR = "${WORKDIR}/deploy-${PN}"
|
|
SSTATETASKS += "do_deploy"
|
|
do_deploy[sstate-inputdirs] = "${DEPLOYDIR}"
|
|
do_deploy[sstate-outputdirs] = "${DEPLOY_DIR_IMAGE}"
|
|
|
|
python do_deploy_setscene () {
|
|
sstate_setscene(d)
|
|
}
|
|
addtask do_deploy_setscene
|
|
do_deploy[dirs] = "${DEPLOYDIR} ${B}"
|