This test script is based around only a strict subset of the SPDK configuration options. If we don't clean before building, we could still have libraries in build/lib from previous tests that the external_code Makefiles do not account for when linking libspdk.so, which will include *all* libraries in build/lib. Fixes issue #1662. Fixes issue #1665. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I525ea1740313048fc44f26b5b0db9ab38161725e Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4970 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: <dongx.yi@intel.com> |
||
---|---|---|
.. | ||
hello_world | ||
passthru | ||
Makefile | ||
README.md | ||
test_make.sh |
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_bdev
is a symlink 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.