Our examples here show how to link in the DPDK environment into an SPDK application. That includes both spdk_env_dpdk library and the DPDK libraries. So put spdk_env_dpdk in the DPDK_LIB variable in the Makefile. This will also simplify a future patch where we will use pkg-config in this Makefile instead. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I2c389eaa9900dbe5f77ccee536bd4edc0a54cccc Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5673 Community-CI: Broadcom CI Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.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.