From: Dharmik Thakkar <dharmik.thakkar@arm.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: dev@dpdk.org, nd@arm.com, Dharmik Thakkar <dharmik.thakkar@arm.com>
Subject: [dpdk-dev] [PATCH 2/2] doc: update build guide for armv8 crypto PMD
Date: Thu, 5 Nov 2020 09:33:16 -0600 [thread overview]
Message-ID: <20201105153316.27918-2-dharmik.thakkar@arm.com> (raw)
In-Reply-To: <20201105153316.27918-1-dharmik.thakkar@arm.com>
Remove build steps about using meson option armv8_crypto_dir.
Add build steps about using pkg-config.
Suggested-by: Thomas Monjalon <thomas@monjalon.net>
Signed-off-by: Dharmik Thakkar <dharmik.thakkar@arm.com>
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
---
doc/guides/cryptodevs/armv8.rst | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/doc/guides/cryptodevs/armv8.rst b/doc/guides/cryptodevs/armv8.rst
index f0f30fe0003a..8963f66a206c 100644
--- a/doc/guides/cryptodevs/armv8.rst
+++ b/doc/guides/cryptodevs/armv8.rst
@@ -37,11 +37,17 @@ To build DPDK with this virtual crypto PMD, the user is required to:
make
-* Build DPDK with meson option ``-Darmv8_crypto_dir=<path_to_AArch64cryptolib>``:
+* Add path to `libAArch64crypto.pc` in `PKG_CONFIG_PATH` environment variable:
.. code-block:: console
- meson -Darmv8_crypto_dir=<path_to_AArch64cryptolib> build
+ export PKG_CONFIG_PATH=<path_to_AArch64cryptolib>/pkgconfig/:$PKG_CONFIG_PATH
+
+* Build DPDK:
+
+.. code-block:: console
+
+ meson build
ninja -C build
The corresponding device can be created only if the following features
--
2.17.1
next prev parent reply other threads:[~2020-11-05 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 15:33 [dpdk-dev] [PATCH 1/2] crypto/armv8: update meson build Dharmik Thakkar
2020-11-05 15:33 ` Dharmik Thakkar [this message]
2020-11-06 1:39 ` [dpdk-dev] [PATCH 2/2] doc: update build guide for armv8 crypto PMD Ruifeng Wang
2020-11-05 16:11 ` [dpdk-dev] [PATCH 1/2] crypto/armv8: update meson build Bruce Richardson
2020-11-13 9:29 ` Thomas Monjalon
2020-11-13 9:39 ` Thomas Monjalon
2020-11-06 1:40 ` Ruifeng Wang
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=20201105153316.27918-2-dharmik.thakkar@arm.com \
--to=dharmik.thakkar@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).