Since devtool uses externalsrc to override vars B and S, references to WORKDIR in do_install result in failures. Is using WORKDIR to resolve to file paths a valid usage? If not, should we warn users and request them to change it when using such a recipe with devtool? Is there any other way to replace references to WORKDIR?
Anuj - apologies for the delay in reviewing this. Do you have an example of a recipe where this resulted in a failure? I just tested a couple that I found with ${WORKDIR} in do_install (nss and keymaps in OE-Core) and they worked fine, so I think there are additional factors at work here - perhaps S = "${WORKDIR}" or otherwise using ${WORKDIR}/something to refer to a file within ${S} or ${B}?
(In reply to comment #1) > Anuj - apologies for the delay in reviewing this. Do you have an example of > a recipe where this resulted in a failure? At the time, I was working on ixgbe recipe in meta-intel. > I just tested a couple that I > found with ${WORKDIR} in do_install (nss and keymaps in OE-Core) and they > worked fine, so I think there are additional factors at work here - perhaps > S = "${WORKDIR}" or otherwise using ${WORKDIR}/something to refer to a file > within ${S} or ${B}? Yes, I just checked and this recipe is using ${WORKDIR}/something to refer to a file in source tree.
FWIW, this is still a valid bug: https://patchwork.yoctoproject.org/project/ti/patch/20220908202054.3800302-1-denis@denix.org/ Should devtool at least warn about such usage? Also, should this be re-assigned to Saul (new devtool owner) now?
Bulk move from 4.99 or 0.00 to 5.99
Needs retesting after the UNPACKDIR changes.