* [ffmpeg] do not pull in postproc for LGPL build
* [ffmpeg] disable avisynthplus on static builds (as it is not functional)
* [ffmpeg] bump port version
* [ffmpeg] x-add-version
Add a missing, but required task for Azure DevOps Pipelines, to automatically authenticate against the Artifacts registry.
This should help any vcpkg newcomer to integrate easily.
file(RENAME Camel lower) works fine when running vcpkg in
Windows Powershell with triplet x64-windows in NTFS fs.
file(RENAME Camel lower) does not work fine when running vcpkg in
WSL with triplet x64-linux in NTFS.
* [klein] new port
* [klein] Replace version-string by version
* [klein] Add call to vcpkg_fixup_pkgconfig()
* [klein] Replace klein by ${PORT}
* [klein] Add patch to avoid using FetchContent
* [klein] Change version to version-date
* update version
* Apply suggestions from code review
Co-authored-by: nicole mazzuca <83086508+strega-nil-ms@users.noreply.github.com>
* Update git-tree version
Co-authored-by: Jonliu1993 <13720414433@163.com>
Co-authored-by: nicole mazzuca <83086508+strega-nil-ms@users.noreply.github.com>
* [OpenSSL]: support for "no-autoload-config" config option
OpenSSL has "no-autoload-config" config option,
which disables automatic config loading:
https://github.com/openssl/openssl/pull/5959
This patch allows to set above option via variable
in custom triplet:
# build-openssl-no-autoload-config.cmake
set(OPENSSL_NO_AUTOLOAD_CONFIG ON)
and use it like:
vcpkg install --overlay-triplets=<path-to-triplets> \
openssl:build-openssl-no-autoload-config
Signed-off-by: Lev Stipakov <lev@openvpn.net>
* [OpenSSL] bump version
Signed-off-by: Lev Stipakov <lev@openvpn.net>
* Expand Architecture list with escape chars
This expands the architecture lists with escape characters. When
building FAT binaries for macos using multiple architectures in the
values they need to be escaped otherwise they are passed on to CMake
incorrectly #14932
* Adding the architecture fix to vcpkg-cmake port
updating port vcpkg-cmake version
* updated version in baseline
* Allow building ffmpeg for multiple architectures on macOS
Since ffmpeg does _not_ support multi-arch builds due to their use of
autotools and config.h which then includes the wrong platform-dependent
functions, we must perform two separate builds and join them using lipo
* fixup! Allow building ffmpeg for multiple architectures on macOS
* fixup! Allow building ffmpeg for multiple architectures on macOS
Co-authored-by: Sander Cox <sander@paralleldimension.nl>
Co-authored-by: Martijn Otto <martijn@resolume.com>
* Expand Architecture list with escape chars
This expands the architecture lists with escape characters. When
building FAT binaries for macos using multiple architectures in the
values they need to be escaped otherwise they are passed on to CMake
incorrectly #14932
* Adding the architecture fix to vcpkg-cmake port
updating port vcpkg-cmake version
* updated version in baseline
* [recast] Export unofficial target
* update version record
* Export INTERFACE_INCLUDE_DIRECTORIES
* Export more include dirs.
* Update versions/r-/recast.json
* Fix mongo-c-driver for custom VCPKG_BUILD_TYPE
* Update version
* Update ports/mongo-c-driver/portfile.cmake
* Update versions/m-/mongo-c-driver.json
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
Co-authored-by: Billy Robert ONeal III <bion@microsoft.com>
* Fix an unconditional #pragma warning breaking other compilers.
* Increase fmt version
* re-ran vcpkg x-add-version --all --overwrite-version, this time it produced a different result for some reason
* [geographiclib] Update to version 1.52
* run ./vcpkg x-add-version geographiclib
* ports/geographiclib/vcpkg.json: version-string -> version
* Another iteration with x-add-version
* After filing an issue with TBB (https://github.com/oneapi-src/oneTBB/issues/414), I found out that building the library with exceptions explicitly disabled as I had added support for had gone from not officially supported to more explicitly disallowed
* update tbb port-version
* run x-add-version
* Fix several issues with the Halide port after v12
1. Use vcpkg-cmake and vcpkg-cmake-config ports
2. Fix usage file to point to relevant documentation
3. Remove OpenGL feature (Halide 12 dropped support)
4. Drop VCPKG_POLICY_EMPTY_PACKAGE
5. Set new Halide packaging variables for better vcpkg compliance.
* update versions
* [llvm] update to 12.0.0, enable zlib and libxml2
* [llvm] disable libxml2 by default, arm64-windows should be supported
* [llvm] try to fix build with ffi on Windows #17663
* [llvm] re-enable libxml2
* [llvm] fix formatting
* [llvm] overwrite version
* [mesa] update to v21.1.0
* [llvm] update ci.baseline
* [halide] update to the latest master commit
* [llvm] disable libxml2 port until complete PR #15390
* update versions
* [llvm] fix disabling of external libraries
* update version
* update ci.baseline
* update ci.baseline
* fix typo
* [llvm] fix libxml2 (depends on #17945)
* revert "[halide] update to the latest master commit"
* update versions
* [halide] fix zlib dependency for tools
* update versions
* [halide] update to official release v12.0.0
* update versions
* [halide] update to v12.0.1
* update version
* [mesa] remove llvm from defaults
* update version
* update ci.baseline
* [mesa] update to v21.1.2 and fix build with LLVM on Windows
* [llvm] allow to build libunwind project on Windows
* update versions
* [mesa] update ci.baseline.txt to disable x64-windows-static-md, may be fixed in the PR #18495
