payloads/edk2: Separate the build target and repository
commit91564fc370323a5ba7caf7d7a4db265531545561
authorSean Rhodes <sean@starlabs.systems>
Fri, 22 Jul 2022 09:10:38 +0000 (22 10:10 +0100)
committerMartin Roth <martin.roth@amd.corp-partner.google.com>
Sat, 8 Oct 2022 20:57:20 +0000 (8 20:57 +0000)
tree524ee4258f77b8a04263d6b23c1cadfd5e2d44ef
parent325afdaf9fd58e6bbfc6884c86e1ea1d5c92b678
payloads/edk2: Separate the build target and repository

Until recently, there were two options to build edk2, UefiPayloadPkg and
CorebootPayloadPkg. Now, there is only one, UefiPayloadPkg but soon,
there will be Universal Payload.

It makes more sense, as the official edk2 repository doesn't work with
coreboot, to have the build target and repository separate. That will
allow for building either UefiPayloadPkg or Universal Payload from the
official repository, MrChromebox' fork or a custom repository.

Signed-off-by: Sean Rhodes <sean@starlabs.systems>
Change-Id: If7f12423058ef69838741f384495ca766ccea083
Reviewed-on: https://review.coreboot.org/c/coreboot/+/66080
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Lean Sheng Tan <sheng.tan@9elements.com>
payloads/external/Makefile.inc
payloads/external/edk2/Kconfig