From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Vincent Jardin <vjardin@free.fr>
Subject: [Buildroot] [PATCH 2/2] package/dpdk: make the libvirt dependency explicit
Date: Sat, 29 Aug 2026 00:11:44 +0200 [thread overview]
Message-ID: <20260828221147.2883191-2-thomas.petazzoni@bootlin.com> (raw)
In-Reply-To: <20260828221147.2883191-1-thomas.petazzoni@bootlin.com>
examples/vm_power_manager/meson.build in DPDK detects the presence of
libvirt:
opt_dep = cc.find_library('virt', required : false)
and then builds some examples or not depending on the availability of
libvirt. Let's make this optional dependency explicit in dpdk.mk, even
if there's no explicit enable/disable option for it.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
package/dpdk/dpdk.mk | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/dpdk/dpdk.mk b/package/dpdk/dpdk.mk
index 147bdb23d3..968a5a877d 100644
--- a/package/dpdk/dpdk.mk
+++ b/package/dpdk/dpdk.mk
@@ -112,6 +112,10 @@ ifeq ($(BR2_PACKAGE_LIBBPF),y)
DPDK_DEPENDENCIES += libbpf
endif
+ifeq ($(BR2_PACKAGE_LIBVIRT),y)
+DPDK_DEPENDENCIES += libvirt
+endif
+
ifeq ($(BR2_PACKAGE_RDMA_CORE),y)
DPDK_DEPENDENCIES += rdma-core
endif
--
2.55.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-28 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 22:11 [Buildroot] [PATCH 1/2] package/dpdk: fix example build issue when libvirt is present Thomas Petazzoni via buildroot
2026-08-28 22:11 ` Thomas Petazzoni via buildroot [this message]
2026-09-01 14:11 ` [Buildroot] [PATCH 2/2] package/dpdk: make the libvirt dependency explicit Peter Korsgaard
2026-09-01 14:10 ` [Buildroot] [PATCH 1/2] package/dpdk: fix example build issue when libvirt is present 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=20260828221147.2883191-2-thomas.petazzoni@bootlin.com \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vjardin@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.