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 <gak...@marvell.com>
Signed-off-by: Bruce Richardson <bruce.richard...@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
