Skip to content

Commit

Permalink
use PKG_CONFIG_EXECUTABLE instead of setting PATH.
Browse files Browse the repository at this point in the history
  • Loading branch information
scareything committed Nov 15, 2024
1 parent aaf87c5 commit 4efcfcb
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions vcpkg-overlays/full-distro/windows-11/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,18 @@ Anyway, here's what worked for me:
pacman -S mingw-w64-x86_64-pkg-config mingw-w64-x86_64-protobuf-c mingw-w64-x86_64-json-c mingw-w64-x86_64-libuv \
mingw-w64-x86_64-libsodium mingw-w64-x86_64-openssl

3. Add `c:\msys64\mingw64\bin` to your PATH.

4. Add the following to your cmake preset:
3. Add the following to your cmake preset:

"cacheVariables": {
"PKG_CONFIG_EXECUTABLE": "c:/msys64/mingw64/bin/pkg-config.exe",
"VCPKG_OVERLAY_PORTS": "${sourceDir}/vcpkg-overlays/full-distro/windows-11"
},
"environment": {
"OPENSSL_ROOT_DIR": "c:/msys64/mingw64"
},

The openssl variable was needed because [cmake's FindOpenSSL module](https://cmake.org/cmake/help/latest/module/FindOpenSSL.html)
does not consult `pkg-config` on Windows.
- Note that the `PKG_CONFIG_EXECUTABLE` setting depends on where you installed `msys2`.
- The openssl variable was needed because [cmake's FindOpenSSL module](https://cmake.org/cmake/help/latest/module/FindOpenSSL.html)
does not consult `pkg-config` on Windows.

5. Remove your build directory, and re-run cmake.

0 comments on commit 4efcfcb

Please sign in to comment.