DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 2/2] app/test: make crypto scheduler an optional dependency
Date: Thu, 28 Sep 2023 12:04:50 +0100	[thread overview]
Message-ID: <20230928110450.862698-2-bruce.richardson@intel.com> (raw)
In-Reply-To: <20230928110450.862698-1-bruce.richardson@intel.com>

The cryptodev autotests make use of the crypto scheduler driver when it
is available, but build fine without. We can therefore remove the hard
dependency on that driver when building the crypto test files.

Fixes: 50823f30f0c8 ("test: build using per-file dependencies")

Reported-by: Akhil Goyal <gakhil@marvell.com>
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 app/test/meson.build | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app/test/meson.build b/app/test/meson.build
index 80b60f68b2..bf9fc90612 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -7,7 +7,7 @@ sources += files('commands.c', 'test.c')
 
 # optional dependencies: some files may use these - and so we should link them in -
 # but do not explicitly require them so they are not listed in the per-file lists below
-optional_deps = []
+optional_deps = ['crypto_scheduler']
 
 # some other utility C files, providing functions used by various tests
 # so we need to include these deps in the dependency list for the files using those fns.
@@ -15,7 +15,7 @@ packet_burst_generator_deps = ['net']
 sample_packet_forward_deps = ['net_ring', 'ethdev', 'bus_vdev']
 virtual_pmd_deps = ['ethdev', 'net', 'bus_pci']
 # test_cryptodev has material that other crypto tests need
-test_cryptodev_deps = ['bus_vdev', 'net', 'cryptodev', 'crypto_scheduler', 'security']
+test_cryptodev_deps = ['bus_vdev', 'net', 'cryptodev', 'security']
 
 source_file_deps = {
     # The C files providing functionality to other test cases
-- 
2.39.2


  reply	other threads:[~2023-09-28 11:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28  9:26 [PATCH] app/test: drop dependency on crypto scheduler driver Bruce Richardson
2023-09-28  9:36 ` [EXT] " Akhil Goyal
2023-09-28  9:45   ` David Marchand
2023-09-28  9:55     ` Bruce Richardson
2023-09-28 11:04 ` [PATCH 1/2] app/test: add support for optional dependencies Bruce Richardson
2023-09-28 11:04   ` Bruce Richardson [this message]
2023-09-28 12:50   ` David Marchand
2023-09-28 13:06     ` [EXT] " Akhil Goyal
2023-09-28 14:42       ` David Marchand

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=20230928110450.862698-2-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.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).