95b76c4dcc
The files for external_code tests were copies of the same files in SPDK. Intention of external_code tests is to verify that nothing breaks in regards to building process. The copies were getting out of sync with functional changes. So to address this: - hello_bdev app is now symlinked - vbdev_passthrough is copied from respective files - RPC and name of the module were changed to not conflict with the original passthrough module Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Idb83b8a06dea7143505d2062b23bfb35c86e3274 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4804 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
914 B
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.