numam-spdk/test/external_code
Darek Stojaczyk 49473bdc81 test/common: consolidate test params for running with external DPDK
Get rid of WITH_DPDK_DIR and SPDK_RUN_INSTALLED_DPDK,
introduce SPDK_RUN_EXTERNAL_DPDK which can point to
a DPDK dir. It's an empty string by default.

Change-Id: Iff2b3773a4614db07f4196165087a79472e02b9a
Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/867
Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-08-17 11:56:32 +00:00
..
hello_world dpdkbuild: build dpdk with meson+ninja 2020-07-24 22:06:11 +00:00
passthru test/autobuild: verify external code can link to libs 2020-04-15 22:10:08 +00:00
Makefile test/autobuild: verify external code can link to libs 2020-04-15 22:10:08 +00:00
README.md test/autobuild: verify external code can link to libs 2020-04-15 22:10:08 +00:00
test_make.sh test/common: consolidate test params for running with external DPDK 2020-08-17 11:56:32 +00:00

This directory is meant to demonstrate how to link an external application and bdev module to the SPDK libraries. The makefiles contain six examples of linking against spdk libraries. They cover linking an application both with and without a custom bdev. For each of these categories, they also demonstrate linking against the spdk combined shared library, individual shared libraries, and static libraries.

This directory also contains a convenient test script, test_make.sh, which automates making SPDK and testing all six of these linker options. It takes a single argument, the path to an SPDK repository and should be run as follows:

sudo ./test_make.sh /path/to/spdk

The application hello_world and bdev module passthru_external have been copied from their namesakes in the top level SPDK github repository and don't have any special functionality.