[Windows] Need help figuring out why vcpkg curl port doesn't get linked #2542

andreamancuso · 2024-06-23T09:23:31Z

andreamancuso
Jun 23, 2024

Hi,
Sorry if this isn't the right place to request help on this issue. I followed these instructions and I got this:

I tried using x64 Native Tools Command Prompt for VS 2022 as instructed. I also tried using x64 Native Tools Command Prompt for VS 2019 but that yielded the exact same result.

I have searched for similar discussions and found: #982 however my issue seems to be a bit different?

Apologies if this looks silly to you. I started doing WebAssembly development using C++ and Dear Imgui less than 2 months ago - this is the first time I'm attempting to build something for x64-Windows (normally I use emscripten).

Full output

C:\dev\maplibre-native>cmake . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
-- The CXX compiler identification is MSVC 19.40.33808.0
-- The C compiler identification is MSVC 19.40.33808.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring GL-Native with OpenGL renderer backend
Parsing public/common/TracyVersion.hpp file
VERSION 0.10.0
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - not found
-- Found Threads: TRUE
-- TRACY_ENABLE: ON
-- TRACY_ON_DEMAND: OFF
-- TRACY_CALLSTACK: OFF
-- TRACY_NO_CALLSTACK: OFF
-- TRACY_NO_CALLSTACK_INLINES: OFF
-- TRACY_ONLY_LOCALHOST: OFF
-- TRACY_NO_BROADCAST: OFF
-- TRACY_ONLY_IPV4: OFF
-- TRACY_NO_CODE_TRANSFER: OFF
-- TRACY_NO_CONTEXT_SWITCH: OFF
-- TRACY_NO_EXIT: OFF
-- TRACY_NO_SAMPLING: OFF
-- TRACY_NO_VERIFY: OFF
-- TRACY_NO_VSYNC_CAPTURE: OFF
-- TRACY_NO_FRAME_IMAGE: OFF
-- TRACY_NO_SYSTEM_TRACING: OFF
-- TRACY_PATCHABLE_NOPSLEDS: OFF
-- TRACY_DELAYED_INIT: OFF
-- TRACY_MANUAL_LIFETIME: OFF
-- TRACY_FIBERS: OFF
-- TRACY_NO_CRASH_HANDLER: OFF
-- TRACY_TIMER_FALLBACK: OFF
-- TRACY_LIBUNWIND_BACKTRACE: OFF
-- TRACY_SYMBOL_OFFLINE_RESOLVE: OFF
-- TRACY_LIBBACKTRACE_ELF_DYNLOAD_SUPPORT: OFF
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2023-08-09/vcpkg.exe -> Z:\\vcpkg.exe... done.
Validating signature... done.

vcpkg package management program version 2023-08-09-9990a4c9026811a312cb2af78bf77f3d9d288416

See LICENSE.txt for license information.
Telemetry
---------
vcpkg collects usage data in order to help us improve your experience.
The data collected by Microsoft is anonymous.
You can opt-out of telemetry by re-running the bootstrap-vcpkg script with -disableMetrics,
passing --disable-metrics to vcpkg on the command line,
or by setting the VCPKG_DISABLE_METRICS environment variable.

Read more about vcpkg telemetry at docs/about/privacy.md
Computing installation plan...
The following packages will be built and installed:
    curl[core,non-http,schannel,ssl,sspi]:x64-windows -> 8.2.1
    dlfcn-win32:x64-windows -> 1.3.1#1
  * egl-registry:x64-windows -> 2022-09-20
    glfw3:x64-windows -> 3.3.8#2
    icu[core,tools]:x64-windows -> 73.1
    libjpeg-turbo:x64-windows -> 3.0.0#1
    libpng:x64-windows -> 1.6.39#1
    libuv:x64-windows -> 1.46.0
    libwebp[core,libwebpmux,nearlossless,simd,unicode]:x64-windows -> 1.3.2
    opengl-registry:x64-windows -> 2022-09-29#1
  * vcpkg-cmake:x64-windows -> 2023-05-04
  * vcpkg-cmake-config:x64-windows -> 2022-02-06#1
  * zlib:x64-windows -> 1.3
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
error: while detecting compiler information:
The log file content at "Z:\buildtrees\detect_compiler\stdout-x64-windows.log" is:
-- Found external ninja('1.11.0').
-- Configuring x64-windows
CMake Error at cripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
    Working Directory: Z:/buildtrees/detect_compiler/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      Z:\buildtrees\detect_compiler\config-x64-windows-rel-CMakeCache.txt.log
      Z:\buildtrees\detect_compiler\config-x64-windows-out.log

Call Stack (most recent call first):
  cripts/cmake/vcpkg_configure_cmake.cmake:314 (vcpkg_execute_required_process)
  cripts/detect_compiler/portfile.cmake:18 (vcpkg_configure_cmake)
  cripts/ports.cmake:147 (include)



error: vcpkg was unable to detect the active compiler's information. See above for the CMake failure output.
CMake Error at C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR)
Call Stack (most recent call first):
  C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
  C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindCURL.cmake:194 (find_package_handle_standard_args)
  platform/windows/vendor/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
  platform/windows/windows.cmake:20 (find_package)
  CMakeLists.txt:1451 (include)


-- Configuring incomplete, errors occurred!

On the other hand, I have followed the instructions on how to build on Linux environment in my Ubuntu WSL2 instance and it worked just fine!

Answered by tdcosta100

Jun 24, 2024

PR #2544 merged to fix this problem.

View full answer

louwers · 2024-06-23T10:04:38Z

louwers
Jun 23, 2024
Maintainer

Maybe @tdcosta100 can give some hints. I am not on Windows myself.

5 replies

andreamancuso Jun 23, 2024
Author

I was able to build it following the Linux instructions using WSL - at least I am not blocked. 👍

On a separate note, I've noticed that the binary mbgl-render clocks in at a hefty ~120MB. I imagine this file size is normal?

tdcosta100 Jun 23, 2024
Collaborator

I'm trying to reproduce the problem, and apparently there is something wrong with vcpkg. I will check what is causing this. My output with a fresh cloned repository is this:

cmake . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
-- The CXX compiler identification is MSVC 19.40.33811.0
-- The C compiler identification is MSVC 19.40.33811.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.40.33807/bin/Hostx86/x86/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.40.33807/bin/Hostx86/x86/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring GL-Native with OpenGL renderer backend
Parsing public/common/TracyVersion.hpp file
VERSION 0.10.0
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - not found
-- Found Threads: TRUE
-- TRACY_ENABLE: ON
-- TRACY_ON_DEMAND: OFF
-- TRACY_CALLSTACK: OFF
-- TRACY_NO_CALLSTACK: OFF
-- TRACY_NO_CALLSTACK_INLINES: OFF
-- TRACY_ONLY_LOCALHOST: OFF
-- TRACY_NO_BROADCAST: OFF
-- TRACY_ONLY_IPV4: OFF
-- TRACY_NO_CODE_TRANSFER: OFF
-- TRACY_NO_CONTEXT_SWITCH: OFF
-- TRACY_NO_EXIT: OFF
-- TRACY_NO_SAMPLING: OFF
-- TRACY_NO_VERIFY: OFF
-- TRACY_NO_VSYNC_CAPTURE: OFF
-- TRACY_NO_FRAME_IMAGE: OFF
-- TRACY_NO_SYSTEM_TRACING: OFF
-- TRACY_PATCHABLE_NOPSLEDS: OFF
-- TRACY_DELAYED_INIT: OFF
-- TRACY_MANUAL_LIFETIME: OFF
-- TRACY_FIBERS: OFF
-- TRACY_NO_CRASH_HANDLER: OFF
-- TRACY_TIMER_FALLBACK: OFF
-- TRACY_LIBUNWIND_BACKTRACE: OFF
-- TRACY_SYMBOL_OFFLINE_RESOLVE: OFF
-- TRACY_LIBBACKTRACE_ELF_DYNLOAD_SUPPORT: OFF
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2023-08-09/vcpkg.exe -> Z:\\vcpkg.exe... done.
Validating signature... done.

vcpkg package management program version 2023-08-09-9990a4c9026811a312cb2af78bf77f3d9d288416

See LICENSE.txt for license information.
Telemetry
---------
vcpkg collects usage data in order to help us improve your experience.
The data collected by Microsoft is anonymous.
You can opt-out of telemetry by re-running the bootstrap-vcpkg script with -disableMetrics,
passing --disable-metrics to vcpkg on the command line,
or by setting the VCPKG_DISABLE_METRICS environment variable.

Read more about vcpkg telemetry at docs/about/privacy.md
Computing installation plan...
The following packages will be built and installed:
    curl[core,non-http,schannel,ssl,sspi]:x86-windows -> 8.2.1
    dlfcn-win32:x86-windows -> 1.3.1#1
  * egl-registry:x86-windows -> 2022-09-20
    glfw3:x86-windows -> 3.3.8#2
  * icu[core,tools]:x64-windows -> 73.1
    icu:x86-windows -> 73.1
    libjpeg-turbo:x86-windows -> 3.0.0#1
    libpng:x86-windows -> 1.6.39#1
    libuv:x86-windows -> 1.46.0
    libwebp[core,libwebpmux,nearlossless,simd,unicode]:x86-windows -> 1.3.2
    opengl-registry:x86-windows -> 2022-09-29#1
  * vcpkg-cmake:x64-windows -> 2023-05-04
  * vcpkg-cmake-config:x64-windows -> 2022-02-06#1
  * zlib:x86-windows -> 1.3
Additional packages (*) will be modified to complete this operation.
error: in triplet x64-windows: Unable to find a valid Visual Studio instance
Could not locate a complete Visual Studio instance
The following paths were examined for Visual Studio instances:
    C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary/Build\vcvarsall.bat

CMake Error at C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR)
Call Stack (most recent call first):
  C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
  C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindCURL.cmake:194 (find_package_handle_standard_args)
  platform/windows/vendor/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
  platform/windows/windows.cmake:20 (find_package)
  CMakeLists.txt:1451 (include)


-- Configuring incomplete, errors occurred!

tdcosta100 Jun 23, 2024
Collaborator

According to microsoft/vcpkg#22074, this is caused by a outdated vcpkg repository. In fact, I updated the repository and now the error is not happening anymore. I'm still making the configure steps, and I will check if everything is building accordingly, then I will commit the necessary changes. For now, you can do the following:

Go to platform\windows\vendor\vcpkg subdirectory
Change to the latest commit with git switch master
Once you are in the latest commit, go back to the repository root directory, and then try to build it

It should work, tell me if not.

tdcosta100 Jun 23, 2024
Collaborator

It worked well, everything was built as expected. I submitted the PR #2544 to correct this.

andreamancuso Jun 24, 2024
Author

Did you run some other commands, clear the cache, etc.? I am still seeing the same error message despite pulling and updating the submodules.

tdcosta100 · 2024-06-24T03:41:00Z

tdcosta100
Jun 24, 2024
Collaborator

PR #2544 merged to fix this problem.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Windows] Need help figuring out why vcpkg curl port doesn't get linked #2542

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 5 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Windows] Need help figuring out why vcpkg curl port doesn't get linked #2542

andreamancuso Jun 23, 2024

Replies: 2 comments · 5 replies

louwers Jun 23, 2024 Maintainer

andreamancuso Jun 23, 2024 Author

tdcosta100 Jun 23, 2024 Collaborator

tdcosta100 Jun 23, 2024 Collaborator

tdcosta100 Jun 23, 2024 Collaborator

andreamancuso Jun 24, 2024 Author

tdcosta100 Jun 24, 2024 Collaborator

andreamancuso
Jun 23, 2024

Replies: 2 comments 5 replies

louwers
Jun 23, 2024
Maintainer

andreamancuso Jun 23, 2024
Author

tdcosta100 Jun 23, 2024
Collaborator

tdcosta100 Jun 23, 2024
Collaborator

tdcosta100 Jun 23, 2024
Collaborator

andreamancuso Jun 24, 2024
Author

tdcosta100
Jun 24, 2024
Collaborator