a091f4c8e0
The SONAME currently written to shared libraries is unversioned, e.g. libazure-core.so. The SDK's ABI is unstable, so replacing these .so files with newer versions will immediately break any consumers. Setting the VERSION property results in libazure-core.so being a symlink that is used at build time to point to the versioned library, e.g. libazure-core.so.1.14.0. Consumers point directly to the versioned library and continue to work against the older version when the library is upgraded. Once rebuilt, they then point to the newer version instead. It is more common to use an ABI version that is separate to the library version, but it makes sense to use the latter when the ABI is unstable. The Boost libraries do exactly this. This change has no effect on static libraries, which is the more common use case. See the CMake documentation for its wider effects. https://cmake.org/cmake/help/latest/prop_tgt/VERSION.html |
||
|---|---|---|
| .. | ||
| azure-security-keyvault-administration | ||
| azure-security-keyvault-certificates | ||
| azure-security-keyvault-keys | ||
| azure-security-keyvault-secrets | ||
| azure-security-keyvault-shared/inc/azure/keyvault/shared | ||
| tools/cleanup | ||
| assets.json | ||
| ci.yml | ||
| CMakeLists.txt | ||
| README.md | ||
| test-resources-post.ps1 | ||
| test-resources.json | ||
| TROUBLESHOOTING.md | ||
Azure Key Vault Client Librares for C++
The Azure Key Vault Client Libraries for C++ allows you to build applications against Microsoft Azure Key Vault services like Keys, Certificates and Secrets. For an overview of Azure Key Vault, see Introduction to Microsoft Azure Key Vault.
Latest release
Find the latest Key Vault client for C++ releases here.