mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Artur Wiebe <artur@4wiebe.de>
To: ptxdist@pengutronix.de
Cc: Artur Wiebe <artur@4wiebe.de>
Subject: [ptxdist] [PATCH 1/2] efivar: new package
Date: Fri, 21 Sep 2018 12:03:03 +0200	[thread overview]
Message-ID: <20180921100304.17321-1-artur@4wiebe.de> (raw)

Signed-off-by: Artur Wiebe <artur@4wiebe.de>
---
 rules/efivar.in   |  8 +++++++
 rules/efivar.make | 59 +++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 67 insertions(+)
 create mode 100644 rules/efivar.in
 create mode 100644 rules/efivar.make

diff --git a/rules/efivar.in b/rules/efivar.in
new file mode 100644
index 000000000..508e412aa
--- /dev/null
+++ b/rules/efivar.in
@@ -0,0 +1,8 @@
+## SECTION=shell_and_console
+
+config EFIVAR
+	tristate
+	select LIBC_DL
+	prompt "efivar"
+	help
+	  Tools and libraries to manipulate EFI variables
diff --git a/rules/efivar.make b/rules/efivar.make
new file mode 100644
index 000000000..105d5a902
--- /dev/null
+++ b/rules/efivar.make
@@ -0,0 +1,59 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2018 by Artur Wiebe <artur@4wiebe.de>
+#
+# See CREDITS for details about who has contributed to this project.
+#
+# For further information about the PTXdist project and license conditions
+# see the README file.
+#
+
+#
+# We provide this package
+#
+PACKAGES-$(PTXCONF_EFIVAR) += efivar
+
+#
+# Paths and names
+#
+EFIVAR_VERSION	:= 36
+EFIVAR_MD5	:= e98140ab7105e90059dc57a67c8c07e9
+EFIVAR		:= efivar-$(EFIVAR_VERSION)
+EFIVAR_SUFFIX	:= tar.bz2
+EFIVAR_URL	:= https://github.com/rhboot/efivar/releases/download/$(EFIVAR_VERSION)/$(EFIVAR).$(EFIVAR_SUFFIX)
+EFIVAR_SOURCE	:= $(SRCDIR)/$(EFIVAR).$(EFIVAR_SUFFIX)
+EFIVAR_DIR	:= $(BUILDDIR)/$(EFIVAR)
+EFIVAR_LICENSE	:= LGPL-2.1-only
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+EFIVAR_CONF_TOOL	:= NO
+EFIVAR_MAKE_ENV		:= $(CROSS_ENV)
+EFIVAR_INSTALL_OPT	:= libdir="/usr/lib/" install
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/efivar.targetinstall:
+	@$(call targetinfo)
+
+	@$(call install_init, efivar)
+	@$(call install_fixup, efivar,PRIORITY,optional)
+	@$(call install_fixup, efivar,SECTION,base)
+	@$(call install_fixup, efivar,AUTHOR,"Artur Wiebe <artur@4wiebe.de>")
+	@$(call install_fixup, efivar,DESCRIPTION,missing)
+
+	@$(call install_lib, efivar, 0, 0, 0644, libefivar)
+	@$(call install_lib, efivar, 0, 0, 0644, libefiboot)
+
+	@$(call install_copy, efivar, 0, 0, 0755, -, /usr/bin/efivar)
+
+	@$(call install_finish, efivar)
+
+	@$(call touch)
+
+
+# vim: syntax=make
-- 
2.19.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2018-09-21 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21 10:03 Artur Wiebe [this message]
2018-09-21 10:03 ` [ptxdist] [PATCH 2/2] efibootmgr: " Artur Wiebe
  -- strict thread matches above, loose matches on Subject: below --
2018-09-11  8:34 [ptxdist] [PATCH 1/2] efivar: " Artur Wiebe
2018-09-17  8:44 ` Michael Olbrich

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=20180921100304.17321-1-artur@4wiebe.de \
    --to=artur@4wiebe.de \
    --cc=ptxdist@pengutronix.de \
    /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