* update to 14.1
* adjust patches
* add lz4 feature on !windows
* version stuff
* [skip actions] patch configure.ac and run autoreconf
* fix some stuff
* [skip actions] more details
* [libpq] Add license filed to vcpkg json
* [libpq] Adjust tcl version to 90g 90s and 90sg
* [libpq] fail early from unsupported features
* [libpq] lake xslt dependent from xml
* [libpq] Update version database
* [libpq] quote static
* [libpq] Update Version Database
Co-authored-by: Alexander Neumann <Alexander.Neumann@hamburg.de>
* [libnoise] Export CMake files
* update version
* format vcpkg.json
* update version
* update patch
* update version
Co-authored-by: Lily Wang <v-lilywang@microsoft.com>
* Trigger some test ports from vcpkg.cmake changes
* Bump test port version
* Revert "Bump test port version"
* Use old toolchain version for parent hashes
* Add ABI hashing note to vcpkg.cmake
* Test vcpkg.cmake with cmake instead vpckg-ci-paraview
* [minizip-ng] fix: in windows only compat symbols were exposed
* [minzip-ng] updated version
* [minzip-ng] updated baseline and versions
* Add vcpkg_check_linkage
* update version
Co-authored-by: prateek.chokse <prateek.chokse@airamatrix.com>
Co-authored-by: Jonliu1993 <13720414433@163.com>
* [Qt6] update to 6.2.4
* adjust patches
* more fixes
* more CMAKE_REQUIRE_FIND_PACKAGE
* fix configure?
* cannot require cmake not config stuff.
* more REQUIRE removals
* adjust required stuff
* more modules.
* less require stuff
* disable env patch for now and silent the require maybe unused. warnings
* different approach
* fix case ?
* fix linux builds
* more stuff to not force in vcpkg
* reenable env patch
* only use env patch on windows.
* reenable qtwebengine. Maybe the ICE was fixed?
* Revert "reenable qtwebengine. Maybe the ICE was fixed?"
This reverts commit 5dc3ca88c1db61a61bcb701d903b042457d85afd.
* version stuff
Co-authored-by: Alexander Neumann <you@example.com>
* [gmp] use native buildsystem on windows
* fix stuff from merge
* fix version
* version stuff
* trying patching some symbols for dynamic builds
* fix nettle build
* fix more dependent ports using gmpd
* fix uwp builds by copying tools
* missing host dep
* fix mpfr
* version-string nettle
* port-version mpfr
* version stuff
* remove patch from portfile
* version stuff
Co-authored-by: Alexander Neumann <you@example.com>
PASSING, REMOVE FROM FAIL LIST: intelrdfpmathlib:x64-linux
PASSING, REMOVE FROM FAIL LIST: ocilib:x64-windows-static
PASSING, REMOVE FROM FAIL LIST: skia:arm64-windows
PASSING, REMOVE FROM FAIL LIST: yato:x64-windows-static-md
REGRESSION: argtable3:arm-uwp
No repro. Maybe fixed by https://github.com/microsoft/vcpkg/pull/23655
REGRESSION: infoware:x64-windows-static
```
-- Found Git: C:/agent/externals/git/cmd/git.exe (found version "2.30.2.windows.1")
Cloning into 'pciids'...
fatal: unable to access 'https://github.com/pciutils/pciids/': Could not resolve host: github.com
CMake Error at CMakeLists.txt:111 (message):
Cloning/pulling pciids repository from https://github.com/pciutils/pciids
failed with 128.
The pci.ids file, downloadable from https://github.com/pciutils/pciids or
http://pci-ids.ucw.cz, is required for building infoware, and cloned
automatically from that GitHub repository by default.
To use a local copy, set INFOWARE_PCI_IDS_PATH to its location.
```
Looks like this port needs to be fixed to work with artifact caching.
REGRESSION: libgpg-error:x64-uwp
```
"D:\buildtrees\libgpg-error\x64-uwp-rel\error-1.42-2324ddbc71.clean\SMP\libgpg-error.sln" (Rebuild target) (1) ->
"D:\buildtrees\libgpg-error\x64-uwp-rel\error-1.42-2324ddbc71.clean\SMP\libgpg-error_winrt.vcxproj" (Rebuild target) (2) ->
(_GetPackageFileExtensions target) ->
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.AppXPackage.Targets(892,25): error MSB4086: A numeric comparison was attempted on "$(TargetPlatformMinVersion)" that evaluates to "" instead of a number, in condition "'$(TargetPlatformMinVersion)' >= '10.0.17200.0'". [D:\buildtrees\libgpg-error\x64-uwp-rel\error-1.42-2324ddbc71.clean\SMP\libgpg-error_winrt.vcxproj]
```
This looks like a VS2022 regression.
REGRESSION: chromium-base:x64-osx
This port is still having the strange behavior where building it once fails but building it again succeeds O_O
REGRESSION: libmikmod:x64-osx
This is emitting a bunch of spew about standard library symbols.
REGRESSION: qtapplicationmanager:x64-windows
Should be fixed by https://github.com/microsoft/vcpkg/pull/23638
* [nspr] Add new port 4.33
* [nss] Add new port 3.73.1
* [nss] Add new port 3.73.1
* Improve code
* Add supports field
* improve code
* version
* Update doc
* [nss] Switch to gyp-nss fork to fix msvc 17 build
* [nss] Improve code
* [nss] Bump version to 3.74
* [nspr] Add new port 4.33
* [nss] Add new port 3.73.1
* improve code
* Update doc
* [nss] Switch to gyp-nss fork to fix msvc 17 build
* [nss] Improve code
* [nss] Bump to 3.74
* [nss] Bump to 3.75
* [nss] Fix mpi.h confusion
When GYP generates rules for ninja, it puts nspr include dirs before nss's
own include dirs. When the msmpi package is installed, this causes
mpi.h from msmpi to be found, instead of multi-precision integer library
that comes bundled with nss.
This patch uses nspr headers from include/nspr subdirectory which sidesteps
the mpi.h from the include root
* [nss] add quotes around paths
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* [nss] remove debug versions of tools
* [nspr] Remove redundant environment variable assignments
* Add dependencies vcpkg-tool-mozbuild and vcpkg-tool-gyp-nss
* clean doc
* version
* Remove unnecessary vcpkg_crosscompiling block on vcpkg-tool-gyp-nss.
Guard for VCPKG_BUILD_TYPE
Improve error reporting for unsupported VCPKG_TARGET_ARCHITECTURE
Declare support for x64 rather than !x86 (given that the URI in question only has x64 binaries)
Fix version numbers to use 'version'.
Co-authored-by: JackBoosY <yuzaiyang@beyondsoft.com>
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
qt5-base[vulkan] feature will introduce --vulkan=yes or --vulkan=no option,
which redundants/confilicts with inherent option -no-vulkan,
which is ambiguous in configure stage.
* bullet3: Add patch for windows-arm64
* bullet3: Add patch for uwp
* Bullet: Remove platform restrictions
Bullet claims to support all platforms. ARM works on android and UWP seems to be taken into consideration.
Vcpkg's restrictions are historical and seem to date back to when the CI was unable to properly test all platforms.
* Update to 3.4.2
* Disable ATL for uwp and for arm64
* Fix linking on uwp
* Fix pc file fixup
* Update versions
* Declare dependency on atlmfc.
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
* [glib] Update to 2.70.5 (microsoft#23647)
See https://github.com/GNOME/glib/commits/glib-2-70 for an
extensive list of changes
* [glibmm] update to 2.70 (microsoft#23649)
See https://github.com/GNOME/glibmm/commits/glibmm-2-70 for an
extensive list of changes
* [glibmm] support msvc2022 (microsoft#23650)
The latest release of glibmm manually configures the v142 compiler
toolchain to be used on msvc2022 environments, which results in
binarycache and export metadata to indicate msvc's v143 compiler
having built the package while it was in fact the v142 toolchain
from the windows sdk.
Upstream has "fixed" this issue, but the patch didn't make it into
the latest release. Apply
https://github.com/GNOME/glibmm/commit/b3a77c3
manually on our side to make sure we use the toolchain we
instructed to be used.
* [libhv] add ssl support
* update version
* [libhv] add ssl support
* fix version
* update version
* revert git-tree
* Add license
* update version
* update version
* update version
* [libhv] add ssl support
* update version
* update portfile.cmake
* update version
