DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: pablo.de.lara.guarch@intel.com
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 1/3] crypto/snow3g: add to meson build
Date: Wed,  1 May 2019 16:53:27 +0100	[thread overview]
Message-ID: <20190501155329.50107-2-bruce.richardson@intel.com> (raw)
Message-ID: <20190501155327.tNVT5bTXN76weyETs9OqftoW7ZaPgxYlSuB2gHTLuO0@z> (raw)
In-Reply-To: <20190501155329.50107-1-bruce.richardson@intel.com>

Snow3G driver is missing support for building with meson. Add a new
meson.build file so it can be included in the builds.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 drivers/crypto/meson.build        |  2 +-
 drivers/crypto/snow3g/meson.build | 13 +++++++++++++
 2 files changed, 14 insertions(+), 1 deletion(-)
 create mode 100644 drivers/crypto/snow3g/meson.build

diff --git a/drivers/crypto/meson.build b/drivers/crypto/meson.build
index bf1bd9286..83e78860e 100644
--- a/drivers/crypto/meson.build
+++ b/drivers/crypto/meson.build
@@ -3,7 +3,7 @@
 
 drivers = ['aesni_gcm', 'aesni_mb', 'caam_jr', 'ccp', 'dpaa_sec', 'dpaa2_sec',
 	'kasumi', 'mvsam', 'null', 'octeontx', 'openssl', 'qat', 'scheduler',
-	'virtio', 'zuc']
+	'snow3g', 'virtio', 'zuc']
 
 std_deps = ['cryptodev'] # cryptodev pulls in all other needed deps
 config_flag_fmt = 'RTE_LIBRTE_@0@_PMD'
diff --git a/drivers/crypto/snow3g/meson.build b/drivers/crypto/snow3g/meson.build
new file mode 100644
index 000000000..c566a5f67
--- /dev/null
+++ b/drivers/crypto/snow3g/meson.build
@@ -0,0 +1,13 @@
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2019 Intel Corporation
+
+lib = cc.find_library('sso_snow3g', required: false)
+if not lib.found() or not cc.has_header('sso_snow3g.h')
+	build = false
+	subdir_done()
+endif
+
+allow_experimental_apis = true
+ext_deps += lib
+sources = files('rte_snow3g_pmd.c', 'rte_snow3g_pmd_ops.c')
+deps += ['bus_vdev', 'cryptodev']
-- 
2.21.0


  parent reply	other threads:[~2019-05-01 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 15:53 [dpdk-dev] [PATCH 0/3] small fixes for crypto drivers Bruce Richardson
2019-05-01 15:53 ` Bruce Richardson
2019-05-01 15:53 ` Bruce Richardson [this message]
2019-05-01 15:53   ` [dpdk-dev] [PATCH 1/3] crypto/snow3g: add to meson build Bruce Richardson
2019-05-01 15:53 ` [dpdk-dev] [PATCH 2/3] crypto/kasumi: fix dependency check Bruce Richardson
2019-05-01 15:53   ` Bruce Richardson
2019-05-01 15:53 ` [dpdk-dev] [PATCH 3/3] crypto/zuc: " Bruce Richardson
2019-05-01 15:53   ` Bruce Richardson
2019-05-02  9:08 ` [dpdk-dev] [PATCH 0/3] small fixes for crypto drivers Thomas Monjalon
2019-05-02  9:08   ` 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=20190501155329.50107-2-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    /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).