63ee471b64
MD040 - Fenced code blocks should have a language specified Fixed all errors Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: Iddd307068c1047ca9a0bb12c1b0d9c88f496765f Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9272 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
18 lines
918 B
Markdown
18 lines
918 B
Markdown
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:
|
|
|
|
~~~bash
|
|
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](https://github.com/spdk/spdk) and don't have any special
|
|
functionality.
|