On Fri, 2017-06-09 at 18:30 -0700, California Sullivan wrote:
> The EFI stub can be used to directly boot a kernel + initramfs.
> This addition was taken from meta-refkit.
>
> Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
> ---
> common/recipes-bsp/systemd-boot/systemd-boot_%.bbappend | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/common/recipes-bsp/systemd-boot/systemd-boot_%.bbappend
> b/common/recipes-bsp/systemd-boot/systemd-boot_%.bbappend
> index f13763b..6cb7369 100644
> --- a/common/recipes-bsp/systemd-boot/systemd-boot_%.bbappend
> +++ b/common/recipes-bsp/systemd-boot/systemd-boot_%.bbappend
> @@ -25,3 +25,11 @@ SRC_URI_append_intel-x86-common = " \
> "
>
> PACKAGE_ARCH_intel-x86-common = "${INTEL_COMMON_PACKAGE_ARCH}"
> +
> +do_compile_append() {
> + oe_runmake linux${SYSTEMD_BOOT_EFI_ARCH}.efi.stub
> +}
> +
> +do_deploy_append() {
> + install ${B}/linux*.efi.stub ${DEPLOYDIR}
> +}
Do these changes make it always build and deploy a stub binary? Should
this be conditional?
Sau!
--
_______________________________________________
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
