summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-phosphor/packagegroups
diff options
context:
space:
mode:
authorWilliam A. Kennington III <wak@google.com>2019-09-17 03:44:48 +0300
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2019-09-23 16:18:15 +0300
commitc230ab38357abbac0fb284e27f16b3894b5af0b2 (patch)
treeba3329817a729b558734dd2753bcfeed13a55d4b /meta-phosphor/recipes-phosphor/packagegroups
parenta0924f60b5f8abec223e9cd0ba4f3b544d277f79 (diff)
downloadopenbmc-c230ab38357abbac0fb284e27f16b3894b5af0b2.tar.xz
image_types_phosphor: Make rwfs name dependent
If we try and generate a `core-image-minimal` and `obmc-phosphor-image` target in the same workspace we will currently encounter an error in bitbake complaining about ``` obmc-phosphor-image-1.0-r0 do_image_complete: The recipe obmc-phosphor-image is trying to install files into a shared area when those files already exist. Those files and their manifest location are: rwfs.jffs2 ``` This patch fixes the complaint by using a distinctly generated rwfs per image type. (From meta-phosphor rev: 8ba81f79c03e673e682079da1f2c62ebb1325645) Change-Id: I5be72cc7d442f5c5853d87de27a57996a6af98e4 Signed-off-by: William A. Kennington III <wak@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-phosphor/recipes-phosphor/packagegroups')
0 files changed, 0 insertions, 0 deletions