[azure-core-cpp] Build error on x64-mingw-dynamic

[PrabhaharanC]

Package: azure-core-cpp[core,curl,http,winhttp]:[email protected]

Host Environment

• Host: x64-windows
• Compiler: GNU 13.2.0
• vcpkg-tool version: 2024-06-10-02590c430e4ed9215d27870138c2e579cc338772 vcpkg-scripts version: 467f9a6a2 2024-06-25 (25 hours ago)

To Reproduce

vcpkg install azure-identity-cpp:x64-mingw-dynamic azure-storage-blobs-cpp:x64-mingw-dynamic

Failure logs

-- Using cached Azure-azure-sdk-for-cpp-azure-core_1.12.0.tar.gz.
-- Cleaning sources at C:/Users/Prabhaharan.C/vcpkg/buildtrees/azure-core-cpp/src/ore_1.12.0-55c344a160.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/Prabhaharan.C/vcpkg/downloads/Azure-azure-sdk-for-cpp-azure-core_1.12.0.tar.gz
-- Using source at C:/Users/Prabhaharan.C/vcpkg/buildtrees/azure-core-cpp/src/ore_1.12.0-55c344a160.clean
CMake Error at ports/azure-core-cpp/portfile.cmake:29 (vcpkg_cmake_configure):
  Unknown CMake command "vcpkg_cmake_configure".
Call Stack (most recent call first):
  scripts/ports.cmake:191 (include)

[Cheney-W]

What you really need to run is: .\vcpkg upgrade and when you are happy with it: .\vcpkg upgrade --no-dry-run Alternatively, you can try: .\vcpkg remove --recurse vcpkg-cmake

[PrabhaharanC]

Thanks for your prompt response. I tried your commands, but i got the same issue again and it says abut curl's port file problem like above. Thanks for helping me in this.

[jimwang118]

You can run the following command in the vcpkg folder:

1. git pull
2. .\bootstrap-vcpkg.bat
3. .\vcpkg install azure-identity-cpp:x64-mingw-dynamic azure-storage-blobs-cpp:x64-mingw-dynamic --binarysource=clear

[PrabhaharanC]

Thanks for reply. Still i got the same issue. Seems port files not correct, i guess. Any chance to install the same in your end? If yes then you can help me with your port files. Because i tried multiple times but i got the same issue. Thanks for helping in this vcpkg issue.

[PrabhaharanC]

Thanks for reply. Still i got the same issue. Seems port files not correct, i guess. Any chance to install the same in your end? If yes then you can help me with your port files. Because i tried multiple times but i got the same issue. Thanks for helping in this vcpkg issue.

Package: azure-core-cpp[core,curl,http,winhttp]:[email protected]

Host Environment

• Host: x64-windows
• Compiler: GNU 13.2.0
• vcpkg-tool version: 2024-06-10-02590c430e4ed9215d27870138c2e579cc338772 vcpkg-scripts version: c247b8108 2024-06-26 (8 hours ago)

To Reproduce

vcpkg install azure-identity-cpp:x64-mingw-dynamic azure-storage-blobs-cpp:x64-mingw-dynamic

Failure logs

-- Downloading https://github.com/Azure/azure-sdk-for-cpp/archive/azure-core_1.12.0.tar.gz -> Azure-azure-sdk-for-cpp-azure-core_1.12.0.tar.gz...
-- Extracting source C:/Users/Prabhaharan.C/vcpkg/downloads/Azure-azure-sdk-for-cpp-azure-core_1.12.0.tar.gz
-- Using source at C:/Users/Prabhaharan.C/vcpkg/buildtrees/azure-core-cpp/src/ore_1.12.0-55c344a160.clean
-- Found external ninja('1.12.1').
-- Configuring x64-mingw-dynamic
-- Building x64-mingw-dynamic-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: "C:/Program Files/CMake/bin/cmake.exe" --build . --config Debug --target install -- -v -j9
    Working Directory: C:/Users/Prabhaharan.C/vcpkg/buildtrees/azure-core-cpp/x64-mingw-dynamic-dbg
    See logs for more information:
      C:\Users\Prabhaharan.C\vcpkg\buildtrees\azure-core-cpp\install-x64-mingw-dynamic-dbg-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/azure-core-cpp/portfile.cmake:38 (vcpkg_cmake_install)
  scripts/ports.cmake:191 (include) 

I got these errors after i reinstalled vcpkg from the scratch. Thank you.

[dg0yt]

https://github.com/Azure/azure-sdk-for-cpp/issues/5745

[github-actions[bot]]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.