azure-storage-cpp | Microsoft Azure Storage Client Library for C | Storage library

For the best development experience, we recommend that developers use the vcpkg as the cross-platform library manager.
To build with source code, there are three ways to install dependencies:.
Via vcpkg You can manage the dependencies with vcpkg, and use Visual Studio 2015 update 3 or Visual Studio 2017 for development environment. Simply installing Casablanca via vcpkg will setup everything needed. C:\src\vcpkg> .\vcpkg install cpprestsdk If you want to build and run test code, you can install UnitTest++ via vcpkg: C:\src\vcpkg> .\vcpkg install unittest-cpp
Via NuGet Because Casablanca does not release NuGet packages anywhere anymore, Starting from 5.1.0, this repository cannot be built with pre-built Casablanca NuGet packages. However, you can export your own version of Casablanca NuGet packages to install dependencies of this project: C:\src\vcpkg> .\vcpkg install cpprestsdk C:\src\vcpkg> .\vcpkg export --nuget cpprestsdk --nuget-id=Casablanca --nuget-version=2.10.18
Manage dependencies by yourself It is not recommended to manage dependencies by yourself. However, you can still build Casablanca by yourself by following these instructions and specify the include directories and link binaries.
As mentioned above, the Azure Storage Client Library for C++ depends on Casablanca. Follow these instructions to compile it.
Clone the project using git:
Install additional dependencies:
Build the SDK for Release:
Install UnitTest++ library:
Build the test code:
Run unit tests
Before building the Azure Storage Client Library on C++, some prerequisites need to be installed first:.
Install prerequisites:
Clone the project using git:
Checkout the version on which Azure Storage Client Library for C++ depends:
Build the project in Release mode
Clone the project using git:
Build the SDK in Release mode:
Clone the project using git:
Build and install the project:
Build the test code:
Run unit tests
Before building the Azure Storage Client Library on C++, some prerequisites need to be installed first:.
Install prerequisites:
Install and enable to use gcc-c++. Note that devtoolset-4 may be not available on some platforms, you can choose to install whichever newer than that, like devtoolset-8.
Download and install boost
Clone the project using git:
Checkout the version on which Azure Storage Client Library for C++ depends:
Build the project in Release mode
Clone the project using git:
Build the SDK in Release mode:
Clone the project using git:
Build and install the project:
Build the test code:
Run unit tests
To build sample code:
To run the samples:
Install dependecies with homebrew:.
Clone the project using git:
If you're using homebrew, there seems to be an issue with the pkg-config files, which means that, by default, a -L flag to tell the linker where libintl lives is left out. We've accounted for this in our CMAKE file, by looking in the usual directory that homebrew puts those libs. If you are not using homebrew, you will get an error stating that you need to tell us where those libs live.
Similarly, for openssl, you don't want to use the version that comes with macOS, it is old. We've accounted for this in the CMAKE script by setting the search paths to where homebrew puts openssl, so if you're not using homebrew you'll need to tell us where a more recent version of openssl lives.
Build the SDK for Release if you are using hombrew:
OR, Build the SDK for Release if you are not using homebrew
<path to Casablanca> to point to your local installation of Casablanca. For example, if the file libcpprest.so exists at location ~/Github/Casablanca/cpprestsdk/Release/build.release/Binaries/libcpprest.dylib, then should be ~/Github/Casablanca/cpprestsdk
<path to openssl> to your local openssl, it is recommended not to use the version that comes with macOS, rather use one from Homebrew or the like. This should be the path that contains the lib and include directories
<path to gettext lib dir> is the directory which contains libintl.dylib
Install UnitTest++ library:
Build the test code:
Run unit tests