summaryrefslogtreecommitdiff
path: root/meta/recipes-extended/procps
diff options
context:
space:
mode:
authorDarren Hart <dvhart@linux.intel.com>2011-12-01 19:20:15 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-12-02 15:28:33 +0000
commit2c4b1675eb3c8c599e3b7f33e459aa608c2b93f2 (patch)
tree277af5c68faa14f389a50516ce06db0d42054048 /meta/recipes-extended/procps
parentd4aef096fb4067d3572ce26a7e25e9b2fb485066 (diff)
downloadopenembedded-core-2c4b1675eb3c8c599e3b7f33e459aa608c2b93f2.tar.gz
openembedded-core-2c4b1675eb3c8c599e3b7f33e459aa608c2b93f2.tar.bz2
openembedded-core-2c4b1675eb3c8c599e3b7f33e459aa608c2b93f2.tar.xz
openembedded-core-2c4b1675eb3c8c599e3b7f33e459aa608c2b93f2.zip
bootimage: Use ${S} explicitly for generated config files
The syslinux and grub-efi classes were generating config files in the current working directory. This caused a failure due to a race in the creation of the directories leading to cwd changing and the build failing to find the config files. While this has been addressed in bitbake, it is better to use an explicit path. While ${WORKDIR} may seem a more appropriate place, the recipe already uses ${S} for the "hdd" and "cd" construction, so we use ${S} here to keep things consolidated and consistent and address the issue with minimal change. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/procps')
0 files changed, 0 insertions, 0 deletions