aboutsummaryrefslogtreecommitdiff
path: root/libraries/flatbuffers
diff options
context:
space:
mode:
authorSteven Voges <svoges.sbo@gmail.com>2022-10-01 01:21:39 +0100
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2022-10-01 09:01:17 +0700
commit5b6917d5a458b02c8f0b6df121a734646bc81a9b (patch)
treebd2d7406e78cbf458bf5ad8d293d08653c6f99db /libraries/flatbuffers
parent92c5d90d28f57287ae90b98bc510b1b589f09dd9 (diff)
libraries/flatbuffers: Updated for version 22.9.24.
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'libraries/flatbuffers')
-rw-r--r--libraries/flatbuffers/README47
-rw-r--r--libraries/flatbuffers/flatbuffers.SlackBuild41
-rw-r--r--libraries/flatbuffers/flatbuffers.info12
-rw-r--r--libraries/flatbuffers/slack-desc12
4 files changed, 57 insertions, 55 deletions
diff --git a/libraries/flatbuffers/README b/libraries/flatbuffers/README
index df4703a18a7b..1f5f7537e442 100644
--- a/libraries/flatbuffers/README
+++ b/libraries/flatbuffers/README
@@ -1,26 +1,27 @@
-FlatBuffers is an efficient cross platform serialization
-library for games and other memory constrained apps. It
-allows you to directly access serialized data without
-unpacking/parsing it first, while still having great
+FlatBuffers is a cross platform serialization library architected for
+maximum memory efficiency. It allows you to directly access serialized
+data without parsing/unpacking it first, while still having great
forwards/backwards compatibility.
-Features:
- - Access to serialized data without parsing/unpacking
- - Memory efficiency and speed. The only memory needed to
- access your data is that of the buffer.
- - Flexible. Optional fields provides forwards and backwards
- compatibility.
- - Tiny code footprint. Small amounts of generated code, and
- just a single small header as the minimum dependency.
- - Strongly typed. Errors happen at compile time.
- - Convenient to use. Generated C++ code allows for terse
- access & construction code.
- - Cross platform code with no dependencies.
+Why use FlatBuffers?
+ * Access to serialized data without parsing/unpacking
+ * Memory efficiency and speed
+ * Flexible
+ * Tiny code footprint
+ * Strongly typed
+ * Convenient to use
+ * Cross platform code with no dependencies
-Protocol Buffers is indeed relatively similar to FlatBuffers,
-with the primary difference being that FlatBuffers does not
-need a parsing/unpacking step to a secondary representation
-before you can access data, often coupled with per-object
-memory allocation. The code is an order of magnitude bigger,
-too. Protocol Buffers has neither optional text import/export
-nor schema language features like unions.
+Why not use Protocol Buffers, or .. ?
+Protocol Buffers is indeed relatively similar to FlatBuffers, with the
+primary difference being that FlatBuffers does not need a parsing/
+unpacking step to a secondary representation before you can access
+data, often coupled with per-object memory allocation. The code is an
+order of magnitude bigger, too. Protocol Buffers has no optional text
+import/export.
+
+If you would like to build the HTML documentation, pass DOCS=yes to
+the build script.
+
+If you would like to include the samples, pass SAMPLES=yes to the
+build script.
diff --git a/libraries/flatbuffers/flatbuffers.SlackBuild b/libraries/flatbuffers/flatbuffers.SlackBuild
index ce9fa731ece4..671d380b122e 100644
--- a/libraries/flatbuffers/flatbuffers.SlackBuild
+++ b/libraries/flatbuffers/flatbuffers.SlackBuild
@@ -1,7 +1,8 @@
#!/bin/bash
-# Slackware build script for Google Flatbuffers
+# Slackware build script for flatbuffers
+# Copyright 2022 Steven Voges <Oregon, USA>
# Copyright 2016 Andre Barboza, Belo Horizonte - Brazil
# All rights reserved.
#
@@ -25,7 +26,9 @@
cd $(dirname $0) ; CWD=$(pwd)
PRGNAM=flatbuffers
-VERSION=${VERSION:-1.12.0}
+VERSION=${VERSION:-22.9.24}
+DOCS=${DOCS:-no}
+SAMPLES=${SAMPLES:-no}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
PKGTYPE=${PKGTYPE:-tgz}
@@ -38,9 +41,6 @@ if [ -z "$ARCH" ]; then
esac
fi
-# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
-# the name of the created package would be, and then exit. This information
-# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
exit 0
@@ -82,11 +82,8 @@ find -L . \
mkdir -p build
cd build
cmake \
- -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
-DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
- -DCMAKE_BUILD_TYPE=Release \
-DCMAKE_INSTALL_PREFIX=/usr \
- -DCMAKE_INSTALL_LIBDIR=/usr/lib${LIBDIRSUFFIX} \
-DFLATBUFFERS_BUILD_FLATC=ON \
-DFLATBUFFERS_BUILD_FLATHASH=ON \
-DFLATBUFFERS_BUILD_FLATLIB=ON \
@@ -95,27 +92,31 @@ cd build
-DFLATBUFFERS_BUILD_TESTS=OFF \
-DFLATBUFFERS_CODE_COVERAGE=OFF \
-DFLATBUFFERS_INSTALL=ON \
- ..
+ -DCMAKE_BUILD_TYPE=Release ..
make
- make install DESTDIR=$PKG
+ make install/strip DESTDIR=$PKG
cd ..
find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \
| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
-find docs/ -type f -exec chmod 644 {} \;
-find samples/ -type f -exec chmod 644 {} \;
-( cd docs/source
- doxygen
-)
-rm docs/source/CONTRIBUTING.md
-cp -rav docs/html docs/source/*.{md,txt} samples/ \
- CONTRIBUTING.md LICENSE.txt \
- $PKG/usr/doc/$PRGNAM-$VERSION
-install -m644 readme.md $PKG/usr/doc/$PRGNAM-$VERSION
+cp -a \
+ *.md LICENSE.txt \
+ $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
+if [ "$DOCS" = "yes" ]; then
+ cd docs/source
+ doxygen
+ cd ../..
+ cp -rav docs/html $PKG/usr/doc/$PRGNAM-$VERSION
+fi
+
+if [ "$SAMPLES" = "yes" ]; then
+ cp -a samples $PKG/usr/doc/$PRGNAM-$VERSION
+fi
+
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
diff --git a/libraries/flatbuffers/flatbuffers.info b/libraries/flatbuffers/flatbuffers.info
index 2a03c03c484a..d2a596226cd7 100644
--- a/libraries/flatbuffers/flatbuffers.info
+++ b/libraries/flatbuffers/flatbuffers.info
@@ -1,10 +1,10 @@
PRGNAM="flatbuffers"
-VERSION="1.12.0"
-HOMEPAGE="https://github.com/google/flatbuffers/"
-DOWNLOAD="https://github.com/google/flatbuffers/archive/v1.12.0/flatbuffers-1.12.0.tar.gz"
-MD5SUM="c62ffefb3d4548b127cca14ce047f16c"
+VERSION="22.9.24"
+HOMEPAGE="https://google.github.io/flatbuffers"
+DOWNLOAD="https://github.com/google/flatbuffers/archive/v22.9.24/flatbuffers-22.9.24.tar.gz"
+MD5SUM="976371c4b47268d09d5cc7827a6a1f6d"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
REQUIRES=""
-MAINTAINER="Andre Barboza"
-EMAIL="bmg.andre@gmail.com"
+MAINTAINER="Steven Voges"
+EMAIL="svoges.sbo@gmail.com"
diff --git a/libraries/flatbuffers/slack-desc b/libraries/flatbuffers/slack-desc
index 3ab4cc661fcd..644d8a354103 100644
--- a/libraries/flatbuffers/slack-desc
+++ b/libraries/flatbuffers/slack-desc
@@ -6,14 +6,14 @@
# customary to leave one space after the ':' except on otherwise blank lines.
|-----handy-ruler------------------------------------------------------|
-flatbuffers: flatbuffers (Efficient cross platform serialization library)
+flatbuffers: flatbuffers (Serialization Library)
+flatbuffers:
+flatbuffers: FlatBuffers: Memory Efficient Serialization Library
+flatbuffers:
+flatbuffers: https://google.github.io/flatbuffers
+flatbuffers:
flatbuffers:
-flatbuffers: FlatBuffers is an efficient cross platform serialization library
-flatbuffers: for games and other memory constrained apps. It allows you to
-flatbuffers: directly access serialized data without unpacking/parsing it
-flatbuffers: first, while still having great forwards/backwards compatibility.
flatbuffers:
flatbuffers:
flatbuffers:
-flatbuffers: https://github.com/google/flatbuffers
flatbuffers: