Package Acquisition using Source / CMake Fetch Content #6309
Labels
Docs
pillar-acquisition
This issue is related to the ability to acquire new customers, one of our core engineering pillars.
Currently, directly including the source for 3rd party dependencies is the most common why C++ developers integrate dependencies into their projects. The Azure SDK for C++ is supposed to support this through CMake Fetch Content, allowing it to take care of downloading the source code at a specific version and linking the build process for the specific Azure SDK library. But it seems our support for CMake Fetch Content has lapsed.
Current CMake Fetch Content Issue:
Project Set Up
Windows Result
On Windows, I hit an issue running the CMake config command:
cmake -B ./build
Our current build process using CMake Fetch Content doesn't seem to either be properly pulling the
wil
dependency or is not properly able to locate the dependency.Linux Result
On Linux (WSL/Ubuntu) I also hit an issue running the CMake config command:
cmake -B ./build
:Seems like this is just a case of missing curl. I installed curl and cleared the CMake cache and tried again. The next dependency I was told was missing was OpenSSL, so again I installed it and reran the config. Then I ran into the following issue:
This new error appears to be caused by missing the azure_macro_utils_c dependency that is required by the SDK's vendored version of azure-uamqp-c. I understand that this could probably also by installing the dependency on my env and moving on, but I question why the build process is attempting to build any part of our AMQP stack when I'm only trying to use our Key Vault Secrets and Identity libraries.
Solutions for building the Azure SDK from source
The text was updated successfully, but these errors were encountered: