From: Ali Alnubani <alialnu@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH] build: install missing header files
Date: Tue, 26 Nov 2019 08:16:58 +0000 [thread overview]
Message-ID: <20191126081637.23008-1-alialnu@mellanox.com> (raw)
The following header files weren't being installed by meson:
- rte_vfio.h
- rte_function_versioning.h
- rte_test.h
This patch adds them to the common_headers list so that
they are installed.
Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
---
lib/librte_eal/common/meson.build | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/lib/librte_eal/common/meson.build b/lib/librte_eal/common/meson.build
index d6a149bec..71d0c50ce 100644
--- a/lib/librte_eal/common/meson.build
+++ b/lib/librte_eal/common/meson.build
@@ -64,6 +64,7 @@ common_headers = files(
'include/rte_eal_interrupts.h',
'include/rte_errno.h',
'include/rte_fbarray.h',
+ 'include/rte_function_versioning.h',
'include/rte_hexdump.h',
'include/rte_hypervisor.h',
'include/rte_interrupts.h',
@@ -84,9 +85,11 @@ common_headers = files(
'include/rte_service_component.h',
'include/rte_string_fns.h',
'include/rte_tailq.h',
+ 'include/rte_test.h',
'include/rte_time.h',
'include/rte_uuid.h',
- 'include/rte_version.h')
+ 'include/rte_version.h',
+ 'include/rte_vfio.h')
# special case install the generic headers, since they go in a subdir
generic_headers = files(
--
2.24.0
next reply other threads:[~2019-11-26 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 8:16 Ali Alnubani [this message]
2019-11-26 9:34 ` Thomas Monjalon
2019-11-26 9:52 ` Bruce Richardson
2019-11-26 10:51 ` [dpdk-dev] [PATCH v2] eal: fix header files install with meson Ali Alnubani
2019-11-26 11:17 ` Thomas Monjalon
2019-11-26 13:25 ` Bruce Richardson
2019-11-26 15:38 ` [dpdk-dev] [PATCH v3] eal: fix header file " Ali Alnubani
2019-11-26 16:13 ` Thomas Monjalon
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=20191126081637.23008-1-alialnu@mellanox.com \
--to=alialnu@mellanox.com \
--cc=dev@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).