From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] network-manager: Add option OpenVSwitch support
Date: Fri, 2 Feb 2018 00:45:16 +0100 [thread overview]
Message-ID: <20180201234516.5031-2-petr.vorel@gmail.com> (raw)
In-Reply-To: <20180201234516.5031-1-petr.vorel@gmail.com>
Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
---
package/network-manager/Config.in | 6 ++++++
package/network-manager/network-manager.mk | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/package/network-manager/Config.in b/package/network-manager/Config.in
index 37e9b2fd8c..72658c1278 100644
--- a/package/network-manager/Config.in
+++ b/package/network-manager/Config.in
@@ -56,6 +56,12 @@ config BR2_PACKAGE_NETWORK_MANAGER_PPPD
comment "pppd support needs a glibc or uClibc toolchain"
depends on BR2_TOOLCHAIN_USES_MUSL
+config BR2_PACKAGE_NETWORK_MANAGER_OVS
+ bool "OpenVSwitch support"
+ select BR2_PACKAGE_JANSSON
+ help
+ This option enables support for OpenVSwitch
+
endif
comment "NetworkManager needs udev /dev management and a glibc toolchain w/ headers >= 3.7, dynamic library"
diff --git a/package/network-manager/network-manager.mk b/package/network-manager/network-manager.mk
index 96e5a0b707..a520aad9c0 100644
--- a/package/network-manager/network-manager.mk
+++ b/package/network-manager/network-manager.mk
@@ -75,7 +75,7 @@ ifeq ($(BR2_PACKAGE_DHCPCD),y)
NETWORK_MANAGER_CONF_OPTS += --with-dhcpcd=/sbin/dhcpcd
endif
-ifeq ($(BR2_PACKAGE_JANSSON),y)
+ifeq ($(BR2_PACKAGE_NETWORK_MANAGER_OVS),y)
NETWORK_MANAGER_CONF_OPTS += --enable-ovs
NETWORK_MANAGER_DEPENDENCIES += jansson
else
--
2.16.1
next prev parent reply other threads:[~2018-02-01 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 23:45 [Buildroot] [PATCH v2 1/2] network-manager: Bump to version 1.10.2 Petr Vorel
2018-02-01 23:45 ` Petr Vorel [this message]
2018-02-02 10:56 ` Thomas Petazzoni
2018-02-02 13:35 ` Petr Vorel
2018-02-03 22:24 ` Peter Korsgaard
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=20180201234516.5031-2-petr.vorel@gmail.com \
--to=petr.vorel@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