This reverts 5b5659850d.
In hindsight I have to admit I did not correctly understand the
implications of the uclibc++.mk include.
The include allows a package to follow the user's choice regarding which
C++ library should be the standard. Linking against uClibc++ instead of
libstd++ is not a problem when running musl (which is what I had
incorrectly assumed), as both C++ libs are separate packages. And
uClibc++ is a lot smaller than libstd++, which is probably why it is
even the default C++ lib on OpenWrt currently.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Provide configuration items to select individual backends. This
also allows to fine-tune the package dependencies.
In order to address #5637, we make this dep unconditionally
until upstream allow to opt-in/opt-out libavahi support.
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
Recently added symbols CONFIG_LIBSSH2_MBEDTLS and CONFIG_LIBSSH2_OPENSSL
require a rerun of ./configure when their selection changes. So add them
to PKG_CONFIG_DEPENDS accordingly.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The change should also work fine with older kernels, as <linux/uaccess.h>
has existed for a long time, and it includes <asm/uaccess.h>.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Make sure that the c++ headers get installed to the staging directory
when libtiffxx was selected/built.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
libxslt already makes sure that the compiler emits position-independent
code. Adding $(FPIC) makes no difference. In addition the libxslt build
system puts its own flag behind the CFLAGS, overriding whatever was set
before.
Also with $(FPIC) in CFLAGS even the libxslt utils get compiled with
PIC, which us undesirable.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
tiff already makes sure that the compiler emits position-independent
code. Adding $(FPIC) makes no difference. In addition the tiff build
system puts its own flag behind the CFLAGS, overriding whatever was set
before.
Also with $(FPIC) in CFLAGS even the tiff utils get compiled with PIC,
which us undesirable.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The include injects a lib depend on libuClibc++.so.0 into the package,
even on musl. Remove it and replace the depend with libstcpp instead.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
libssh2 already makes sure that the compiler emits position-independent
code. Adding $(FPIC) makes no difference. In addition the libssh2 build
system puts its own flag behind the CFLAGS, overriding whatever was set
before.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The sqlite3 binary was linked against the static library of libsqlite3.
It now uses the .so library of the libsqlite3 package. This dropped size
of the sqlite3 binary from 652k to 91k.
Signed-off-by: Gaëtan Buchetet <bubuche.pub@free.fr>
Bumped package version.
There was an issue with .so file:
dependent package wanted lib.so.2.8 but there was
only lib.so.2.8.0 there so one more symlink added.
http-parser sources are owned by nodejs now.
Signed-off-by: Tibor Dudlák <tdudlak@redhat.com>
libgpiod is a C library with corresponding tools for interacting
with the linux GPIO character device (gpiod stands for GPIO device).
Since linux 4.8 the GPIO sysfs interface is deprecated. User space should use
the character device instead. This library encapsulates the ioctl calls and
data structures behind a straightforward API.
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
This adds a choice to menuselect so people can select if they would like
to compile libssh2 against mbedtls (default) or openssl.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The full-text search engine version 3 (FTS3) and R*Tree (RTREE) modules are
enabled by default in sqlite3; add config options which allow to disable these
sqlite lib modules.
Disabling FTS3 reduces the so file with 475KB while disabling RTREE reduces
the so file with 121KB on x86 architecture.
Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
This allows prevents build error due to trust-paths not being
specified. The trust module was not being used in openwrt.
Resolves#5528
Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
