* Fix boost build toolchain options not being used
The issue was due to the options only being set for the gcc toolchain,
and then only for a specific version. On platforms defaulting to a
different toolchain (e.g. macOS) this didn't work at all.
Additionally, some missing flags were not propagated, in particular the
CMAKE_OSX_DEPLOYMENT_TARGET, CMAKE_OSX_SYSROOT and CMAKE_OSX_ARCHITECTURES
* [boost-modular-build-helper] Apply CR comments
Co-authored-by: Martijn Otto <git@martijnotto.nl>
Co-authored-by: Robert Schumacher <ras0219@outlook.com>
* add port: xlsxio
* vcpkg x-add-version xlsxio
* fix deps
* add vcpkg_fixup_pkgconfig()
* Apply suggestions from code review
To be consistent, `OUT_FEATURE_OPTIONS FEATURE_OPTIONS` in a new line, as in `vcpkg_from_git`.
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* Update ports/xlsxio/portfile.cmake
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* format
* use date as version string
* vcpkg format-manifest
* Update ports/xlsxio/portfile.cmake
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* patch for dependency
* fix typo
* vcpkg x-add-version
* remove feature wide
* Update ports/xlsxio/vcpkg.json
deprecate libzip that's an alternative and imperfect
Co-authored-by: Robert Schumacher <roschuma@microsoft.com>
* Update ports/xlsxio/vcpkg.json
Co-authored-by: Robert Schumacher <roschuma@microsoft.com>
* Update versions/x-/xlsxio.json
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* Remove x64-windows-cpp17 community triplet
Co-authored-by: abc <a@b.com>
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
Co-authored-by: Robert Schumacher <roschuma@microsoft.com>
* [ftxui] Add new port (fix#16327)
* [ftxui] x-add-version ftxui
* [ftxui] Drop UWP support
* [ftxui] Update to 2021-06-16
* [ftxui] Overwrite version
* [ftxui] Try to fix linux and macOS build
* [ftxui] Overwrite version
* [ftxui] Fail fast on UWP
* [ftxui] Clean version file
* [ftxui] Overwrite version
* [ftxui] Update to 2021-06-17
* [ftxui] Overwrite version
* [ftxui] Remove debug/share
* [ftxui] Overwrite version
* [ftxui] Quote paths
* [ftxui] Overwrite version
* [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
