* [google-cloud-cpp] Support abseil[cxx17]
Signed-off-by: Daniel Lundborg <daniel.lundborg@sandvik.com>
* [google-cloud-cpp] add version
Signed-off-by: Daniel Lundborg <daniel.lundborg@sandvik.com>
The error shows related to the qt5-3d module when I'm compiling COLMAP 3.6 by vcpkg on Windows 10 with Visual Studio 2022 installed. After tracing the logs, I realized that only assimp-vc143-mt.lib available in VCPKG_ROOT\installed\x64-windows\lib
* Fix boost-exception for wasm32-emscripten
* Updated port version for boost-exception
* Updated boost-exception with x-add-version
* Fixed patch
* Boost-build x-add-version
* Increment boost-build version again
* x-add-version for boost-build
* Fixed boost-build port version
* x-add-version for boost-build
Co-authored-by: Semphris <semphris@protonmail.com>
* [quickcpplib] Avoid deprecated helper functions
* [quickcpplib] Update to version @0.0.0-cad832c8
fixup quickcpplib ref
* [quickcpplib] Add cxx17 and cxx20 feature levels
* [quickcpplib] Update port version information
* [llfio] Update to version @2.0-20220112
* [llfio] Avoid deprecated helper functions
* [llfio] Add cxx17 and cxx20 feature levels
* [llfio] Support static linkage triplets
* [llfio] Always install ntkernel-error-category
ntkernel-error-category sources have been recorded as part of
`headers.cmake` which are added to the library targets. Therefore cmake
configure fails if they aren't available.
* [llfio] Fix msvc crt linkage specification
`quickcpplib` parses `CMAKE_MSVC_RUNTIME_LIBRARY` and cannot support the
default crt linkage generator expression from vcpkg. Therefore we need
to manually specify a valid option.
* [llfio] Update port version information
* [libtcod] Update to 1.20.1
* Current versions do not follow semantic versioning.
Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com>
Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com>
* Do not use pkg-config for finding OpenSSL
Do not use libuv when building for Emscripten
(cherry picked from commit f541d3265a00f31a91a56ed25096a0ad476fd2a9)
* Remove redundant flag
* Update versions
* Update versions
* Fix patch
* Update versions
Co-authored-by: Ahmed Yarub Hani Al Nuaimi <ahmed.alnuaimi@zwift.com>
* [gherkin-c] Fix UNIX build, fix install path
* version
* manifest
* version
* should be a `-` not an `_`
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
* Remove the beta release of the azure-security-keyvault-common-cpp as it
is no longer necessary.
* revert delete operator, set this port as depreciate
* format, version
* Update versions/a-/azure-security-keyvault-common-cpp.json
* Revert "Update versions/a-/azure-security-keyvault-common-cpp.json"
This reverts commit 8b9e666f8e.
* Revert "format, version"
This reverts commit bb7d882f12.
* Revert "revert delete operator, set this port as depreciate"
This reverts commit 8916a559d6.
* Add back the old versions file for keyvault-common.
Co-authored-by: JackBoosY <yuzaiyang@beyondsoft.com>
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* Adding tracy port
* Formatting tracy port
* Tidying up the port
* Formatting again
* Making sure git-tree is correct
* Adding correct vcpkg dependencies
* Newline at file end again
* Update version database
* Making sure to mark tracy as not supporting x86 at all
* Updating version again
* Responding to feedback and double checking which builds will work
* Updating versions
* Tidying up some loose ends
* Updating port version again
* Removing port-version 1
* Removing tracy from ci baseline
* Removing unnecessary include copy
* Updating version
* Resolving feedback
* Updating version and formatting
* Version for the version god
* tweaking tracy supports
* Formatting and version
* Version
* Adding pthreads dependency to tracy for non-windows platforms
* Version
* Fixing tracy port
* Fixing version
* TRACY_IMPORTS should be an INTERFACE define
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
* Update HTTP to HTTPS links where it can be done safely.
This means that the HTTP-based link gave a 200 response with identical
content to the HTTPS version of the link. For links containing
variables, we checked the interpolated (real) link.
* Bump relevant vcpkg.json versions.
* Use version-date for cello.
* update version
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
Co-authored-by: Jonliu1993 <13720414433@163.com>
