Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] gnu-efi: add host variant
Date: Tue, 17 Jul 2018 23:29:45 +0200	[thread overview]
Message-ID: <87601dk0ty.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1530887774-19479-3-git-send-email-celso.neto.cwi@datacom.com.br> (Celso Varella's message of "Fri, 6 Jul 2018 11:36:13 -0300")

>>>>> "Celso" == Celso Varella <celso.neto.cwi@datacom.com.br> writes:

 > It will be required by host-sbsigntools (forthcoming package).
 > Signed-off-by: Carlos Santos <casantos@datacom.com.br>
 > ---
 >  package/gnu-efi/gnu-efi.mk | 20 ++++++++++++++++++++
 >  1 file changed, 20 insertions(+)

 > diff --git a/package/gnu-efi/gnu-efi.mk b/package/gnu-efi/gnu-efi.mk
 > index d55e027..b106010 100644
 > --- a/package/gnu-efi/gnu-efi.mk
 > +++ b/package/gnu-efi/gnu-efi.mk
 > @@ -26,6 +26,12 @@ else ifeq ($(BR2_aarch64)$(BR2_aarch64_be),y)
 >  GNU_EFI_PLATFORM = aarch64
 >  endif
 
 > +ifeq ($(HOSTARCH),x86)
 > +HOST_GNU_EFI_PLATFORM = ia32
 > +else
 > +HOST_GNU_EFI_PLATFORM = $(HOSTARCH)
 > +endif

While host-gnu-efi shouldn't be a user visible config option, it would
still be nice to add a Config.in.host with hidden
BR2_PACKAGE_HOST_GNU_EFI_ARCH_SUPPORTS option depending on the supported
host architectures, so E.G. host-sbsigntools can depend on it.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-07-17 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 14:36 [Buildroot] [PATCH 0/3] New packages to support UEFI Secure Boot Celso Varella
2018-07-06 14:36 ` [Buildroot] [PATCH 1/3] efitools: new package Celso Varella
2018-07-17 20:32   ` Peter Korsgaard
2018-07-06 14:36 ` [Buildroot] [PATCH 2/3] gnu-efi: add host variant Celso Varella
2018-07-17 21:29   ` Peter Korsgaard [this message]
2018-07-06 14:36 ` [Buildroot] [PATCH 3/3] sbsigntools: new package Celso Varella
2018-07-17 21:25   ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87601dk0ty.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox