c006a8da16
-pthread is what SPDK in-tree Makefiles use, so use that in the external_code Makefile too. -pthread can be used both on the compilation and link stages. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I8ef702b8fbde825a4191d961738ebc605b0aa4c5 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5675 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.