mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-08-18 21:33:39 -09:00
2795fecc50
Currently, nftables JSON support is implicit: if jansson is enabled, JSON support is enabled, otherwise it is not. Some packages will require that nftables be built with JSON support; that's the case of netavarks, for example (to come in a later patch). So, in the current state, it would mean a package would have to select jansson, although it does not itself use it, so that nftables has JSON support. This does not feel right. Instead, introduce an option to nftables, to explicitly enabled JSON support. Packages such as netavark would then just have to require JSON support in nftables. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
28 lines
834 B
Plaintext
28 lines
834 B
Plaintext
config BR2_PACKAGE_NFTABLES
|
|
bool "nftables"
|
|
depends on BR2_USE_WCHAR
|
|
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12
|
|
select BR2_PACKAGE_LIBMNL
|
|
select BR2_PACKAGE_LIBNFTNL
|
|
help
|
|
nftables is the project that aims to replace the existing
|
|
{ip,ip6,arp,eb}tables framework.
|
|
Basically, this project provides a new packet filtering
|
|
framework, a new userspace utility and also a compatibility
|
|
layer for {ip,ip6}tables.
|
|
|
|
http://www.netfilter.org/projects/nftables/index.html
|
|
|
|
if BR2_PACKAGE_NFTABLES
|
|
# Legacy: this used to be handled in nftables.mk
|
|
source "package/nftables/nftables-python/Config.in"
|
|
|
|
config BR2_PACKAGE_NFTABLES_JSON
|
|
bool "json support"
|
|
select BR2_PACKAGE_JANSSON
|
|
|
|
endif
|
|
|
|
comment "nftables needs a toolchain w/ wchar, headers >= 3.12"
|
|
depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12
|