Lines Matching refs:shared

119 …DK libraries can be built as both static and shared object files. To facilitate building libraries…
127 SPDK shared objects follow a semantic versioning pattern with a major and minor version. Any change…
128 break backwards compatibility (symbol removal or change) will cause a shared object major increment…
133 major version of each SPDK shared library will increment only once between each SPDK release.
140 `libspdk_bdev.so.3.0` do not necessarily belong to the same release. This also means that shared ob…
147 which is a linker script. It simply contains references to all of the other spdk shared objects.
151 1. An application can link to the top level shared object library as follows:
199 Unlike SPDK shared objects, the filename does not contain any versioning semantics. Linking against
200 static objects is similar to shared objects but will always require the use of `-Wl,--whole-archive`
206 `-L/path/to/static/libs`. The use of static objects instead of shared objects can also be forced
207 through `-Wl,-Bstatic`, otherwise some compilers might prefer to use the shared objects if both