Seth Howell 79602d10c6 module/event: add subsystem interdependencies ... The SPDK application framework defines a list of event subsystem dependencies. When linking against individual shared libraries, it is useful for this dependency structure to be codified in the shared libraries themselves. For example, when linking a bdev based application against libspdk_bdev.so, one might wish to only specify this shared object at link time. However, when you actually run the application, it will fail to start because it is not linked to the copy and vmd subsystems. However, once thesedependencies are added, one can effectively link against only the exact subsystems they need and any dependent subsystems will be linked in automatically. Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/466081 (master) (cherry picked from commit 5c62618f26) Change-Id: Ic986281a162ac20b523486e9f8cccf4a0787afd7 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/466983 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>		2019-09-06 02:19:41 +00:00
..
bdev	mk: move the bdev modules under module directory.	2019-09-06 02:19:41 +00:00
blob	lib/blob: move bdev subdir under module directory.	2019-09-06 02:19:41 +00:00
copy	lib/copy: move ioat subdir to module directory.	2019-09-06 02:19:41 +00:00
event	module/event: add subsystem interdependencies	2019-09-06 02:19:41 +00:00
sock	lib/sock: move subdirs to module/sock	2019-09-06 02:19:41 +00:00
Makefile	module: add shared lib deps for all modules.	2019-09-06 02:19:41 +00:00