ARM64 support
MarkVabulas opened this issue · 3 comments
As a developer on the Hololens 2, and a paying Azure customer of many Azure services, we would like to use Azure-storage-cpp for storing data blobs which can be shared between users of our applications, both on desktop and in the Hololens 2.
Currently, through vcpkg, the triplet arm64-windows is not available, due to the inability to use CppReskSDK on the Hololens 2. The issue stems from the confusion between C++/WinRT projections and C++/CX support. We're following the current Microsoft guidelines for development, in Visual Studio 2019, using native C++/WinRT, /std:c++latest, and not using /ZW. CppRestSDK has been deprecated in favor of the native C++/WinRT HttpClient and MessageWebSocket/StreamWebSocket. Posting a request to have support in the vcpkg github isn't possible given the library dependency on CppRestSDK. It's worth noting that replacing CppRestSDK with C++/WinRT would remove the requirement, reduce maintenance requirements, and streamline your codebase.
What is the possibility of Azure developers having this client library updated to match the current status of the native windows/devices development environment? Surely, replacing CppRestSDK with the current C++/WinRT projections shouldn't be a monumental task. If this is impossible or won't be undertaken by the Azure developers, please advise ASAP. We must decide to try to rewrite the Azure-storage-cpp subsystem using the C++/WinRT projections or potentially even go with a different cloud provider for this service.
Hi @MarkVabulas , this azure-storage-cpp project has been deprecated in favor of our next generation of storage SDK, which doesn't depend on cpprestsdk or boost, and is also compatible with ARM.
If you're starting a new project, I strongly recommend you try the new SDK.
Thank you for this. It's a huge relief. Why do ALL of the Microsoft Documents EVERYWHERE reference this project instead? And why are there no links on this project suggesting to use the newer project? I didn't even know the other one existed after reading through the documentation thoroughly.
We put a notice at the top of README in this project. Maybe other links/documents haven't been updated yet.