NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3f47f2542f
kumquat-buildroot/package/efibootmgr/Config.in

24 lines
954 B
Plaintext
Raw Normal View History

efibootmgr: new package A Linux user-space application to modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This application can create and destroy boot entries, change the boot order, change the next running boot option, and more. The only issue found was that it was trying to include headers from the host, so $(STAGING_DIR) has been prepended to the include path so that the package finds the right headers. efibootmgr depends on the libraries provided by efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> [Thomas: - change the "depends on" for efivar to a "select", and propagate the relevant dependencies. - the license is GPLv2+, not GPLv2. - move the Makefile tweak to a post-patch hook rather than doing it as part of the build step.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-21 03:23:56 +02:00
config BR2_PACKAGE_EFIBOOTMGR
bool "efibootmgr"
efivar: introduce BR2_PACKAGE_EFIVAR_ARCH_SUPPORTS efivar only makes sense on platforms that support UEFI. UEFI is only supported by some architectures at the moment, being mostly employed on platforms such as x86, x86_64 and aarch64. Some other platforms such as MIPS and PowerPC may have some unofficial UEFI support. UEFI is also limited to little endian architectures. efivar was being supported in Buildroot without architecture restrictions so far, however this has led to the creation of a number of hacks in the recipes, mostly for architectures that are not supported by UEFI. In order to avoid spending more time to debug these failures and maintaining more hacks for unsupported architectures, efivar can be restricted to that platforms where it makes sense and where it is more likely to receive some testing and actual usage. The existing hacks for the now unsupported architectures are removed, and the dependency is propagated to efibootmgr as it depends on efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-06 00:07:17 +01:00
depends on BR2_PACKAGE_EFIVAR_ARCH_SUPPORTS # efivar
efivar: not available for static builds efivar uses dlfcn.h which is not available in static builds configuration. Also propagate dependency to efibootmgr. This commit also does s/requires/needs/ in comment while at it. Fixes: http://autobuild.buildroot.net/results/ab3/ab32ccacfac2e65e1fcb307058d06c3d0122979d/ Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-05 17:08:22 +01:00
depends on !BR2_STATIC_LIBS # efivar
efibootmgr: new package A Linux user-space application to modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This application can create and destroy boot entries, change the boot order, change the next running boot option, and more. The only issue found was that it was trying to include headers from the host, so $(STAGING_DIR) has been prepended to the include path so that the package finds the right headers. efibootmgr depends on the libraries provided by efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> [Thomas: - change the "depends on" for efivar to a "select", and propagate the relevant dependencies. - the license is GPLv2+, not GPLv2. - move the Makefile tweak to a post-patch hook rather than doing it as part of the build step.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-21 03:23:56 +02:00
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12 # efivar
efibootmgr: fix reverse dependency from efivar efivar minimum gcc version dependency changed from 4.7 to 4.9 in the last efivar bump, so this must be reflected in efibootmgr Config.in as well. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-02 21:15:37 +02:00
depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 # efivar
efivar: introduce BR2_PACKAGE_EFIVAR_ARCH_SUPPORTS efivar only makes sense on platforms that support UEFI. UEFI is only supported by some architectures at the moment, being mostly employed on platforms such as x86, x86_64 and aarch64. Some other platforms such as MIPS and PowerPC may have some unofficial UEFI support. UEFI is also limited to little endian architectures. efivar was being supported in Buildroot without architecture restrictions so far, however this has led to the creation of a number of hacks in the recipes, mostly for architectures that are not supported by UEFI. In order to avoid spending more time to debug these failures and maintaining more hacks for unsupported architectures, efivar can be restricted to that platforms where it makes sense and where it is more likely to receive some testing and actual usage. The existing hacks for the now unsupported architectures are removed, and the dependency is propagated to efibootmgr as it depends on efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-06 00:07:17 +01:00
depends on !BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS
efibootmgr: new package A Linux user-space application to modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This application can create and destroy boot entries, change the boot order, change the next running boot option, and more. The only issue found was that it was trying to include headers from the host, so $(STAGING_DIR) has been prepended to the include path so that the package finds the right headers. efibootmgr depends on the libraries provided by efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> [Thomas: - change the "depends on" for efivar to a "select", and propagate the relevant dependencies. - the license is GPLv2+, not GPLv2. - move the Makefile tweak to a post-patch hook rather than doing it as part of the build step.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-21 03:23:56 +02:00
select BR2_PACKAGE_EFIVAR
efibootmgr: explicitly depend on host-pkgconf and popt efibootmgr uses host-pkgconf and popt, so explicitly add them to _DEPENDENCIES instead of relying on them getting pulled in by efivar. [Peter: reword as suggested by Thomas] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-03-23 10:57:40 +01:00
select BR2_PACKAGE_POPT
efibootmgr: new package A Linux user-space application to modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This application can create and destroy boot entries, change the boot order, change the next running boot option, and more. The only issue found was that it was trying to include headers from the host, so $(STAGING_DIR) has been prepended to the include path so that the package finds the right headers. efibootmgr depends on the libraries provided by efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> [Thomas: - change the "depends on" for efivar to a "select", and propagate the relevant dependencies. - the license is GPLv2+, not GPLv2. - move the Makefile tweak to a post-patch hook rather than doing it as part of the build step.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-21 03:23:56 +02:00
help
A Linux user-space application to modify the Intel Extensible
package/e*: fix wrapping of Config.in help text The check-package script when ran gives warnings on text wrapping on all of these Config files. This patch cleans up all warnings related to the text wrapping for the Config files starting with the letter e in the package directory. The appropriate indentation is: <tab><2 spaces><62 chars> See http://nightly.buildroot.org/#writing-rules-config-in for more information. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-31 15:53:41 +02:00
Firmware Interface (EFI) Boot Manager. This application can
create and destroy boot entries, change the boot order, change
the next running boot option, and more.
efibootmgr: new package A Linux user-space application to modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This application can create and destroy boot entries, change the boot order, change the next running boot option, and more. The only issue found was that it was trying to include headers from the host, so $(STAGING_DIR) has been prepended to the include path so that the package finds the right headers. efibootmgr depends on the libraries provided by efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> [Thomas: - change the "depends on" for efivar to a "select", and propagate the relevant dependencies. - the license is GPLv2+, not GPLv2. - move the Makefile tweak to a post-patch hook rather than doing it as part of the build step.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-21 03:23:56 +02:00
efibootmgr: bump version Drop 0001-dont-use-fshort-wchar-when-building.patch and 0003-Remove-extra-const-keywords-gcc-7-gripes-about.patch as they are now upstream. The upstream repo moved to the 'rhboot' github project, so adjust upstream URL in .mk and help text to match. Version 15 introduces build time configuration of the default EFI directory (E.G. the subdirectory in the EFI system partition where the loader is installed). This used to be hardcoded to redhat, but now a value must be specified at build time. Given that, it is unlikely that people relied on the default value so set it to the more sensible 'buildroot'. While we are at it, also add a hash for the license file. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-03-22 13:51:53 +01:00
https://github.com/rhboot/efibootmgr
efibootmgr: new package A Linux user-space application to modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This application can create and destroy boot entries, change the boot order, change the next running boot option, and more. The only issue found was that it was trying to include headers from the host, so $(STAGING_DIR) has been prepended to the include path so that the package finds the right headers. efibootmgr depends on the libraries provided by efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> [Thomas: - change the "depends on" for efivar to a "select", and propagate the relevant dependencies. - the license is GPLv2+, not GPLv2. - move the Makefile tweak to a post-patch hook rather than doing it as part of the build step.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-21 03:23:56 +02:00
efibootmgr: use the new gettext logic This commit switches to use the new gettext logic, which involves: - using TARGET_NLS_DEPENDENCIES instead of hand-encoded dependencies on gettext/host-gettext - using TARGET_NLS_LIBS to force linking against libintl - dropping BR2_PACKAGE_GETTEXT selection The BR2_USE_WCHAR dependency was needed for gettext, now that we no longer need gettext, we can also get rid of this dependency. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-03 22:45:53 +02:00
comment "efibootmgr needs a glibc or uClibc toolchain w/ dynamic library, headers >= 3.12, gcc >= 4.9"
efivar: introduce BR2_PACKAGE_EFIVAR_ARCH_SUPPORTS efivar only makes sense on platforms that support UEFI. UEFI is only supported by some architectures at the moment, being mostly employed on platforms such as x86, x86_64 and aarch64. Some other platforms such as MIPS and PowerPC may have some unofficial UEFI support. UEFI is also limited to little endian architectures. efivar was being supported in Buildroot without architecture restrictions so far, however this has led to the creation of a number of hacks in the recipes, mostly for architectures that are not supported by UEFI. In order to avoid spending more time to debug these failures and maintaining more hacks for unsupported architectures, efivar can be restricted to that platforms where it makes sense and where it is more likely to receive some testing and actual usage. The existing hacks for the now unsupported architectures are removed, and the dependency is propagated to efibootmgr as it depends on efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-06 00:07:17 +01:00
depends on BR2_PACKAGE_EFIVAR_ARCH_SUPPORTS
efivar: not available for static builds efivar uses dlfcn.h which is not available in static builds configuration. Also propagate dependency to efibootmgr. This commit also does s/requires/needs/ in comment while at it. Fixes: http://autobuild.buildroot.net/results/ab3/ab32ccacfac2e65e1fcb307058d06c3d0122979d/ Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-05 17:08:22 +01:00
depends on BR2_STATIC_LIBS || \
!BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12 || \
efibootmgr: use the new gettext logic This commit switches to use the new gettext logic, which involves: - using TARGET_NLS_DEPENDENCIES instead of hand-encoded dependencies on gettext/host-gettext - using TARGET_NLS_LIBS to force linking against libintl - dropping BR2_PACKAGE_GETTEXT selection The BR2_USE_WCHAR dependency was needed for gettext, now that we no longer need gettext, we can also get rid of this dependency. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-03 22:45:53 +02:00
!BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
efivar: introduce BR2_PACKAGE_EFIVAR_ARCH_SUPPORTS efivar only makes sense on platforms that support UEFI. UEFI is only supported by some architectures at the moment, being mostly employed on platforms such as x86, x86_64 and aarch64. Some other platforms such as MIPS and PowerPC may have some unofficial UEFI support. UEFI is also limited to little endian architectures. efivar was being supported in Buildroot without architecture restrictions so far, however this has led to the creation of a number of hacks in the recipes, mostly for architectures that are not supported by UEFI. In order to avoid spending more time to debug these failures and maintaining more hacks for unsupported architectures, efivar can be restricted to that platforms where it makes sense and where it is more likely to receive some testing and actual usage. The existing hacks for the now unsupported architectures are removed, and the dependency is propagated to efibootmgr as it depends on efivar. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-06 00:07:17 +01:00
depends on !BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS
Reference in New Issue Copy Permalink