The way of including freetype headers is by using
#include <ft2build.h>
#include FT_FREETYPE_H
along with $root/include/freetype which has $root/include/freetype/ft2build.h
and then the rest of the headers under $root/include/freetype/freetype2/*.h.
The portfile.cmake moves the headers one directory up into $root/include
so that there's $root/include/ft2build.h and the rest of the headers
under $root/include/freetype/.
This in turn means that the above way of including header files requires
$root/include to be in the include search path. That's not the case by
default and the generated freetype-config.cmake also doesn't include
that.
Therefore the freetype config approach results in failing builds when
applications wants to use it. This is easy to reproduce using
find_package(Freetype CONFIG REQUIRED)
...
target_link_libraries(foo PRIVATE freetype)
As a remedy, this patch fixes the freetype-config.cmake file to add
$root/include in the include search path.
* [gdk-pixbuf] Fix Linux compilation.
Unlike #6625 this version contains the minimal changes required
to keep other dependencies as untouched as possible.
* [gdk-pixbuf] Bumping CONTROL versions
* [libcroco] Added copy pdbs to portfile.
* [libcroco] Fix missing unoficial-libcroco-targets-debug.cmake...
... file from installation.
Referenced file
vcpkg/installed/x64-windows/tools/zxing-cpp/zxing.exe
did not exist, because it was created at
vcpkg/installed/x64-windows/tools/zxing/zxing.exe
Closes#6616
With the new version we should not need the patch, so I removed it. We
also moved the repository from GoogleCloudPlatform to the googleapis/
GitHub organization, save a redirect in the download by fixing that.
Update from the latest release 0.19 to use the latest snapshot
LibRaw-201903 (SHA-1:d4f05dd1b9b2d44c8f7e82043cbad3c724db2416).
The rationale is that LibRaw publishes:
- snapshots every 5-7 months (in master branch)
- releases (0.18, 0.19, etc.) every 1-1.5 years.
- security hotfixes for releases (0.19.1, 0.19.2, etc.)
Hence, from user point of view, it is practical to refer to
the latest snapshot, instead of the latest release.
Another issue is that the latest release 0.19 does not include
support for C++17 (does not allow to replace std::auto_ptr with
std::unique_ptr). The latest LibRaw-201903 includes related fixes.
