From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/libfuse3: new package
Date: Fri, 17 Apr 2020 16:18:55 +0300 [thread overview]
Message-ID: <20200417131855.4803-1-asafka7@gmail.com> (raw)
The package is separated from the regular libfuse package, as it
contains new API (and can co-exist with libfuse).
Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
v1->v2:
* Use two spaced for hash file indentation
* Bump to latest version
* Remove redundant LIBFUSE3_SOURCE
* Use the 'github' macro
Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
DEVELOPERS | 1 +
package/Config.in | 1 +
package/libfuse3/Config.in | 14 ++++++++++++++
package/libfuse3/libfuse3.hash | 3 +++
package/libfuse3/libfuse3.mk | 26 ++++++++++++++++++++++++++
5 files changed, 45 insertions(+)
create mode 100644 package/libfuse3/Config.in
create mode 100644 package/libfuse3/libfuse3.hash
create mode 100644 package/libfuse3/libfuse3.mk
diff --git a/DEVELOPERS b/DEVELOPERS
index 3d9c976a95..99d9ba3b7d 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -259,6 +259,7 @@ F: configs/raspberrypi4_64_defconfig
N: Asaf Kahlon <asafka7@gmail.com>
F: package/collectd/
+F: package/libfuse3/
F: package/libuv/
F: package/python*
F: package/snmpclitools/
diff --git a/package/Config.in b/package/Config.in
index ccf54f2417..43bdbdfda8 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -1359,6 +1359,7 @@ menu "Filesystem"
source "package/libconfig/Config.in"
source "package/libconfuse/Config.in"
source "package/libfuse/Config.in"
+ source "package/libfuse3/Config.in"
source "package/liblockfile/Config.in"
source "package/libnfs/Config.in"
source "package/libsysfs/Config.in"
diff --git a/package/libfuse3/Config.in b/package/libfuse3/Config.in
new file mode 100644
index 0000000000..584d3bf132
--- /dev/null
+++ b/package/libfuse3/Config.in
@@ -0,0 +1,14 @@
+config BR2_PACKAGE_LIBFUSE3
+ bool "libfuse3"
+ depends on !BR2_STATIC_LIBS
+ depends on BR2_TOOLCHAIN_HAS_THREADS
+ depends on BR2_USE_MMU # fork()
+ help
+ The reference implementation of the Linux FUSE
+ (Filesystem in Userspace) interface.
+
+ https://github.com/libfuse/libfuse
+
+comment "libfuse3 needs a toolchain w/ threads, dynamic library"
+ depends on BR2_USE_MMU
+ depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
diff --git a/package/libfuse3/libfuse3.hash b/package/libfuse3/libfuse3.hash
new file mode 100644
index 0000000000..bc09da4cf8
--- /dev/null
+++ b/package/libfuse3/libfuse3.hash
@@ -0,0 +1,3 @@
+# Locally calculated sha256 checksums
+sha256 4f3dea4979c30fbd85f46b8812bee5945bd6bb4487165eb01ecde57bbfbb332f libfuse3-3.9.1.tar.gz
+sha256 b8832d9caaa075bbbd2aef24efa09f8b7ab66a832812d88c602da0c7b4397fad LICENSE
diff --git a/package/libfuse3/libfuse3.mk b/package/libfuse3/libfuse3.mk
new file mode 100644
index 0000000000..d23d8d9a43
--- /dev/null
+++ b/package/libfuse3/libfuse3.mk
@@ -0,0 +1,26 @@
+################################################################################
+#
+# libfuse3
+#
+################################################################################
+
+LIBFUSE3_VERSION = 3.9.1
+LIBFUSE3_SITE = $(call github,libfuse,libfuse,fuse-$(LIBFUSE3_VERSION))
+LIBFUSE3_LICENSE = LGPL-2.1
+LIBFUSE3_LICENSE_FILES = LICENSE
+LIBFUSE3_INSTALL_STAGING = YES
+LIBFUSE3_DEPENDENCIES = $(if $(BR2_PACKAGE_LIBICONV),libiconv)
+LIBFUSE3_CONF_OPTS = \
+ -Dexamples=false \
+ -Dudevrulesdir=/lib/udev/rules.d \
+ -Duseroot=false
+
+define LIBFUSE3_DEVICES
+ /dev/fuse c 666 0 0 10 229 0 0 -
+endef
+
+define LIBFUSE3_PERMISSIONS
+ /usr/bin/fusermount3 f 4755 0 0 - - - - -
+endef
+
+$(eval $(meson-package))
--
2.26.0
next reply other threads:[~2020-04-17 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 13:18 Asaf Kahlon [this message]
2020-04-19 13:02 ` [Buildroot] [PATCH v2 1/1] package/libfuse3: new package Yann E. MORIN
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=20200417131855.4803-1-asafka7@gmail.com \
--to=asafka7@gmail.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