d/numam-spdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
05d92eaff7
numam-spdk/test/external_code
History
Seth Howell 150b9f6219 test/external_code: set LD_LIBRARY_PATH once. 
Just set it once instead of doing it over and over.
This cleans up the code a lot.

Signed-off-by: Seth Howell <seth.howell@intel.com>
Change-Id: I91c6ea8c02d964693909b9c53795b0f1ee09c90f
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2979
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-06-30 07:56:40 +00:00
..
hello_world test/autobuild: verify external code can link to libs 2020-04-15 22:10:08 +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/external_code: set LD_LIBRARY_PATH once. 2020-06-30 07:56:40 +00:00

README.md

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.