diff options
author | Lee Nipper <lee.nipper@linux.com> | 2015-08-12 23:08:52 -0500 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-08-19 17:57:56 +0100 |
commit | 12551f4ca214cfc2528b42da8574a6622228ce0b (patch) | |
tree | cf50e2bd81624bb966eaf38fbb839bcb6361965e /meta/recipes-devtools/rpm | |
parent | 4b779616ed3fe96519fa3be9c32aad1bb0f1ea3f (diff) | |
download | openembedded-core-12551f4ca214cfc2528b42da8574a6622228ce0b.tar.gz openembedded-core-12551f4ca214cfc2528b42da8574a6622228ce0b.tar.bz2 openembedded-core-12551f4ca214cfc2528b42da8574a6622228ce0b.zip |
u-boot.inc: Add UBOOT_BINARY sym links for UBOOT_CONFIG types
An additional use case of UBOOT_CONFIG is when a machine has applicability
to boards of the same architecture but different in other ways
to require a different UBOOT_BINARY build.
The UBOOT_CONFIG default value can be a list of these board types.
For example:
UBOOT_CONFIG ??= "boardA boardB"
UBOOT_CONFIG[boardA] = "boardA_defconfig"
UBOOT_CONFIG[boardB] = "boardB_defconfig"
Change do_install and do_deploy sections which process a UBOOT_CONFIG list
to create short symbolic links to each of the config types for UBOOT_BINARY.
This is similar to the links currently being created for
SPL_BINARY when it is defined with a UBOOT_CONFIG list.
For the above example, and UBOOT_BINARY as u-boot.bin,
the additional symbolic links created in the DEPLOYDIR would be
u-boot.bin-boardA
u-boot.bin-boardB
Signed-off-by: Lee Nipper <lee.nipper@linux.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-devtools/rpm')
0 files changed, 0 insertions, 0 deletions