DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: web@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>
Subject: [dpdk-web] [PATCH] add build system update as nice to have
Date: Fri, 17 Jan 2020 13:19:13 +0000
Message-ID: <20200117131913.72621-1-ferruh.yigit@intel.com> (raw)

Some headers in DPDK needs to be shared between various libraries, these
are treated as public header by build system and put into same folder,
other libraries can consume the header from this folder.
But this cause a side affect that internal headers exposed to the
application.

A simple sample of this is 'rte_cryptodev_pmd.h', it is provided by
'cryptodev' library and used by crypto PMDs, but this headers shouldn't
be used by applications.

A solution can be using two different interim folders, one for public
headers and other for DPDK wide headers. DPDK components can look both
folders but only ones in the public header folder will be installed to
system folders.

Cc: David Marchand <david.marchand@redhat.com>

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
 content/roadmap/_index.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 6cb2e68..ea920bb 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -49,6 +49,7 @@ This list is obviously neither complete nor guaranteed.
 - default configuration from files
 - generic white/blacklisting
 - libedit integration
+- don't expose DPDK wide header to public, like rte_cryptodev_pmd.h
 
 ### Cycle model {#cycle}
 ----
-- 
2.24.1


             reply	other threads:[~2020-01-17 13:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 13:19 Ferruh Yigit [this message]
2020-01-17 13:29 ` Richardson, Bruce
2020-01-18  0:10   ` Honnappa Nagarahalli

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=20200117131913.72621-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=web@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

DPDK website maintenance

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/web/0 web/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 web web/ https://inbox.dpdk.org/web \
		web@dpdk.org
	public-inbox-index web

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.web


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git