rare case, but let other not waste time trying to fix it

master
Pierre Joye 2021-08-27 05:03:58 +07:00
parent 81716a06f4
commit 284a2c6cae
1 changed files with 6 additions and 2 deletions

View File

@ -61,7 +61,7 @@ the required libraries, vcpkg can install them automatically. The steps are:
1. Install vcpkg, see https://vcpkg.io/en/getting-started.html
2. Choose the vcpkg architecture
SET VCPKG_DEFAULT_TRIPLET="x64-windows" (or add pkgname:x64-windows)
SET VCPKG_DEFAULT_TRIPLET=x64-windows (or add pkgname:x64-windows)
3. install the dependencies needed for the build. F.e.
C:\vcpkg\vcpkg.exe install libpng libjpeg-turbo freetype tiff libheif libwebp
4. add -DCMAKE_TOOLCHAIN_FILE=[path to c:\path\to\vcpkg]\scripts\buildsystems\vcpkg.cmake
@ -69,4 +69,8 @@ the required libraries, vcpkg can install them automatically. The steps are:
It is then not needed to manually add CMAKE_INCLUDE_PATH or CMAKE_LIBRARY_PATH as options.
See the https://vcpkg.io for more informations about vcpkg and how to customize an install.
See the https://vcpkg.io for more informations about vcpkg and how to customize an install.
Randomly, you may cmake may fail to find the dependencies, with vcpkg at least up to 2021-08-12-85ab112d5ee102bc6eac8cdbbfdd173a71374e04 (as of the time of writing).
So far the only way to fix it is to reinstall vcpkg and then install the dependencies again. See https://github.com/microsoft/vcpkg/issues/13614,
especially my comment on the 27th of August 2021 and follow ups.