From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/5] gnu-efi: new package
Date: Wed, 19 Feb 2014 18:53:38 +0100 [thread overview]
Message-ID: <20140219175338.GA3400@free.fr> (raw)
In-Reply-To: <1392766441-2160-3-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2014-02-19 00:33 +0100, Thomas Petazzoni spake thusly:
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Christophe Vu-Brugier <cvubrugier@yahoo.fr>
[--SNIP--]
> diff --git a/package/gnu-efi/gnu-efi.mk b/package/gnu-efi/gnu-efi.mk
> new file mode 100644
> index 0000000..28eb17e
> --- /dev/null
> +++ b/package/gnu-efi/gnu-efi.mk
> @@ -0,0 +1,40 @@
> +################################################################################
> +#
> +# gnu-efi
> +#
> +################################################################################
> +
> +GNU_EFI_VERSION = 3.0u
> +GNU_EFI_SOURCE = gnu-efi_$(GNU_EFI_VERSION).orig.tar.gz
> +GNU_EFI_SITE = http://downloads.sourceforge.net/project/gnu-efi/
> +GNU_EFI_INSTALL_STAGING = YES
> +GNU_EFI_LICENSE = GPLv2+ (gnuefi), BSD (efilib)
> +GNU_EFI_LICENSE_FILES = debian/copyright
> +
> +ifeq ($(BR2_i386),y)
> +GNU_EFI_PLATFORM=ia32
> +else ifeq ($(BR2_x86_64),y)
> +GNU_EFI_PLATFORM=x86_64
> +endif
Shouldn't we do like for grub: some EFI-BIOS on x86-64 machines might be
a 32-bit EFI-BIOS, in which case we'd want to build the 32-bit version
even if the target is 64-bit?
> +define GNU_EFI_BUILD_CMDS
> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) \
> + $(TARGET_CONFIGURE_OPTS) \
> + ARCH=$(GNU_EFI_PLATFORM)
> +endef
> +
> +define GNU_EFI_INSTALL_TARGET_CMDS
> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) \
> + $(TARGET_CONFIGURE_OPTS) \
> + INSTALLROOT=$(TARGET_DIR) \
> + PREFIX=/usr ARCH=$(GNU_EFI_PLATFORM) install
> +endef
> +
> +define GNU_EFI_INSTALL_STAGING_CMDS
> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) \
> + $(TARGET_CONFIGURE_OPTS) \
> + INSTALLROOT=$(STAGING_DIR) \
> + PREFIX=/usr ARCH=$(GNU_EFI_PLATFORM) install
> +endef
Why install in target/ and staging/, and not in images/ ?
Also, this is used to build EFI applications, so I'd expect some host
tools to be built and isntalled, too. What am I missing?
(Hmm... Maybe I should look at the rest of the series...)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-02-19 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 23:33 [Buildroot] [PATCH v2 0/5] Various x86 bootloaders and board support Thomas Petazzoni
2014-02-18 23:33 ` [Buildroot] [PATCH v2 1/5] grub2: add new package Thomas Petazzoni
2014-02-18 23:33 ` [Buildroot] [PATCH v2 2/5] gnu-efi: " Thomas Petazzoni
2014-02-19 17:53 ` Yann E. MORIN [this message]
2014-02-19 18:57 ` Thomas Petazzoni
2014-02-19 19:06 ` Yann E. MORIN
2014-02-18 23:33 ` [Buildroot] [PATCH v2 3/5] gummiboot: " Thomas Petazzoni
2014-02-19 17:59 ` Yann E. MORIN
2014-02-19 18:59 ` Thomas Petazzoni
2014-02-19 19:08 ` Yann E. MORIN
2014-02-18 23:34 ` [Buildroot] [PATCH v2 4/5] board: add support for the MinnowBoard Thomas Petazzoni
2014-02-18 23:34 ` [Buildroot] [PATCH v2 5/5] board: add support for the Fri2 board Thomas Petazzoni
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=20140219175338.GA3400@free.fr \
--to=yann.morin.1998@free.fr \
--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