a66fde23d7
Static compilation for external_code tests uses SYS_LIBS that now includes libvfio-user. As such the COMMON_CFLAGS need to point to the build directory. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I6f3aa670a62445088535eacdfa1483bfacd5ce7b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6020 Community-CI: Broadcom CI Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
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.