From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>, dev@dpdk.org
Cc: thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru,
bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH] ethdev: introduce enable_driver_sdk to install driver headers
Date: Fri, 12 Mar 2021 15:19:36 +0000 [thread overview]
Message-ID: <2da8b376-9016-11e6-8891-6db3957c7d79@intel.com> (raw)
In-Reply-To: <1615490833-23052-1-git-send-email-roretzla@linux.microsoft.com>
On 3/11/2021 7:27 PM, Tyler Retzlaff wrote:
> Introduce a meson option enable_driver_sdk when true installs internal
> driver headers for ethdev. this allows drivers that do not depend on
> stable api/abi to be built external to the dpdk source tree.
>
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> ---
>
> it's still unclear to me if we should be renaming the headers:
>
> ethdev_driver.h -> rte_ethdev_driver.h
> ethdev_pci.h -> rte_ethdev_pci.h
> ethdev_vdev.h -> rte_ethdev_vdev.h
>
> lib/librte_ethdev/meson.build | 5 +++++
> meson_options.txt | 2 ++
> 2 files changed, 7 insertions(+)
>
> diff --git a/lib/librte_ethdev/meson.build b/lib/librte_ethdev/meson.build
> index c37b2e377..7ecdec6f0 100644
> --- a/lib/librte_ethdev/meson.build
> +++ b/lib/librte_ethdev/meson.build
> @@ -20,6 +20,11 @@ headers = files('rte_ethdev.h',
> 'rte_mtr_driver.h',
> 'rte_tm.h',
> 'rte_tm_driver.h')
> +if get_option('enable_driver_sdk')
> +headers += files('ethdev_driver.h',
> + 'ethdev_pci.h',
> + 'ethdev_vdev.h')
> +endif
Instead of adding the "get_option('enable_driver_sdk')" checks to the modules,
what about a more generic solution, like:
modules assign relevant headers into a new variable, let's say 'pmd_headers',
and in a high level meson file, all 'pmd_headers' are installed if
'enable_driver_sdk' enabled?
next prev parent reply other threads:[~2021-03-12 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 19:27 Tyler Retzlaff
2021-03-12 15:19 ` Ferruh Yigit [this message]
2021-03-12 15:25 ` David Marchand
2021-03-12 15:34 ` Bruce Richardson
2021-03-12 15:52 ` Thomas Monjalon
2021-03-12 18:43 ` Tyler Retzlaff
2021-03-12 22:20 ` [dpdk-dev] [PATCH v2] " Tyler Retzlaff
2021-03-15 10:06 ` Bruce Richardson
2021-03-23 17:04 ` Ferruh Yigit
2021-03-24 4:32 ` Tyler Retzlaff
2021-03-24 11:27 ` Ferruh Yigit
2021-03-24 11:30 ` Thomas Monjalon
2021-03-24 16:24 ` Tyler Retzlaff
2021-03-26 12:02 ` Ferruh Yigit
2021-03-26 20:52 ` Tyler Retzlaff
2021-03-29 9:43 ` Ferruh Yigit
2021-03-29 12:10 ` Thomas Monjalon
2021-03-29 15:23 ` Ferruh Yigit
2021-03-29 19:31 ` Thomas Monjalon
2021-03-30 12:50 ` Ferruh Yigit
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=2da8b376-9016-11e6-8891-6db3957c7d79@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).