* [xerces-c] Update to 3.2.2
* [xalan-c] Build against xerces-c 3.2.2 and include extra patches
* [xalan-c] Use new vcpkg_extract_source_archive_ex()
* [xerces-c] Use vcpkg_fixup_cmake_targets
* [xerces-c] Disable vcpkg_test_cmake due to misbehavior in x64
* [xerces-c] Remove bin directory when building static
* [xalan-c] Modernize
* Correctly configure GTK3 to reflect recomended release settings
GTK/Glib packaging guidelines recomends a release build to use debugging
facilities set to level 'minimum'. Disabling this is officially not
recomended for stable releases. For more info read the following link,
the section `--enable-debug`.
https://developer.gnome.org/glib/stable/glib-building.html#extra-configuration-options
* [gtk] Bump control version
* [libusb] Update to 1.0.22
* Update version to v1.0.22 tag instead of non-release commit hash.
* Remove libusb-usbdk output library.
The two Windows backends have been unified. The UsbDk backend is
selectable at runtime using the function libusb_set_option().
* Remove libfreenect2 patch (changes integrated upstream).
* Tidy up portfile.
* [libusb] Use vcpkg_install_msbuild()
* [libfreenect2] Add missing libjpeg-turbo dependency
* making sure there is a leading <compileflags> even if CMAKE_CXX_FLAGS do not start with a whitespace
* making sure there is a leading <compileflags> even if CMAKE_CXX_FLAGS do not start with a whitespace
* full support for CXXFLAGS, CFLAGS and LDFLAGS throughout the boost-modular-build-helper
* [boost-modular-build-helper] Bump version and use CMAKE_* macros since the VCPKG_* macros are not passed in
* [boost-type-erasure] Depend on boost-thread even in UWP
* [orc] add apache orc library
* [orc] Simplify patch. Note in usage that no targets are available. Don't build tools on windows because they are not supported.
* [orc] Move tools to tools/orc/ to fix Linux build.
* [orc] fix tools ouput folder
* Fix crc32c CMake configuration directory.
The port was installing the CMake configuration files for Crc32c in
share/crc32c/Crc32c/Crc32cConfig.cmake, where find_package() cannot
find them. They should be installed in share/crc32c/Crc32cConfig.cmake.
* [crc32] Lowercase share directory
Response files are a convenient way of specifying bulk parameters,
typically supported by compilers and linkers. For vcpkg response files
provide a convenient way of installing sets of packages from simple
newline separate list files.
The word Privacy was capitalized for no reason. I've also added to word programming so that it's clear that the document refers to programming languages, before it referred only to language.
