]> code.ossystems Code Review - openembedded-core.git/commit
bootimage: Use ${S} explicitly for generated config files
authorDarren Hart <dvhart@linux.intel.com>
Fri, 2 Dec 2011 03:20:15 +0000 (19:20 -0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 2 Dec 2011 15:28:33 +0000 (15:28 +0000)
commit2c4b1675eb3c8c599e3b7f33e459aa608c2b93f2
tree277af5c68faa14f389a50516ce06db0d42054048
parentd4aef096fb4067d3572ce26a7e25e9b2fb485066
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>
meta/classes/grub-efi.bbclass
meta/classes/syslinux.bbclass