5c62618f26
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. Change-Id: Ic986281a162ac20b523486e9f8cccf4a0787afd7 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/466081 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> |
||
---|---|---|
.. | ||
nvme.libtest.mk | ||
spdk.app_cxx.mk | ||
spdk.app_vars.mk | ||
spdk.app.mk | ||
spdk.common.mk | ||
spdk.deps.mk | ||
spdk.lib_deps.mk | ||
spdk.lib.mk | ||
spdk.mock.unittest.mk | ||
spdk.modules.mk | ||
spdk.subdirs.mk | ||
spdk.unittest.mk |