Host Environment
- OS: x64-windows
- Compiler: VS2019?
- vcpkg date of last pull: 12/3/2020
To Reproduce
Steps to reproduce the behavior:
./vcpkg install cairo
cairo will install fontconfig and then link against it
Run depends.exe or similar on cairo.dll found in .../installed/x64-windows/bin
cairo.dll will be dependent on "libfontconfig-1.dll"
But the fontconfig package installs "fontconfig-1.dll"
so load of the DLL will fail
Failure logs
Additional context
The Cairo cmake cache shows it finding the correct fontconfig.lib file, but in the /lib directory, fontconfig.def ends with "LIBRARY libfontconfig-1.dll", and the .lib file references libfontconfig-1.dll so Cairo is linking to the DLL fontconfig provides, but it doesn't exist as FontConfig actually outputs fontconfig-1.dll (which would be the correct windows naming convention).
Recommend altering the fontconfig build to target that naming standard.
Host Environment
To Reproduce
Steps to reproduce the behavior:
./vcpkg install cairocairo will install fontconfig and then link against it
Run depends.exe or similar on cairo.dll found in .../installed/x64-windows/bin
cairo.dll will be dependent on "libfontconfig-1.dll"
But the fontconfig package installs "fontconfig-1.dll"
so load of the DLL will fail
Failure logs
Additional context
The Cairo cmake cache shows it finding the correct fontconfig.lib file, but in the /lib directory, fontconfig.def ends with "LIBRARY libfontconfig-1.dll", and the .lib file references libfontconfig-1.dll so Cairo is linking to the DLL fontconfig provides, but it doesn't exist as FontConfig actually outputs fontconfig-1.dll (which would be the correct windows naming convention).
Recommend altering the fontconfig build to target that naming standard.