During the configuration of harfbuzz several Python scripts are invoked
that are supposed to copy some files. For some reason however the
scripts end up being instructed to copy files to themselves at which
point a SameFileError is risen, causing the build to fail.
This is a workaround for the underlaying issue that is deemed to be
usptream. The upstream issues are
- https://github.com/mesonbuild/meson/issues/8375
- https://github.com/harfbuzz/harfbuzz/issues/2870
The workaround is to add a patch that makes sure these scripts check
whether source and target file are the same and only invoking the copy
action if they are not.
Fixes#16262
* Updated the `hazelcast-cpp-client` version to 4.0.1 since we released this new patch release.
* Updated the version for the latest commit using the command `./vcpkg x-add-version --overwrite-version hazelcast-cpp-client`.
* [hazelcast-cpp-client] Restore version 4.0.0 to the db
Co-authored-by: Robert Schumacher <roschuma@microsoft.com>
* [taglib] Upgrade from 1.12-beta-2 to 1.12
- Replace CONTROL with vcpkg.json
- Use Git tag as REF
- Use official version number (without the date suffix)
- Switch to semantic versioning
- Link official homepage instead of GitHub project page
- Add license string according to GitHub repo
- Add missing vcpkg_fixup_pkgconfig() in portfile
* [taglib] Disable depcrecated warnings for MSVC
See also: https://github.com/taglib/taglib/issues/1000
* [taglib] Use VCPKG_LIBRARY_LINKAGE instead of VCPKG_CRT_LINKAGE
https://github.com/microsoft/vcpkg/pull/16390/files#r591427047
* [taglib] vcpkg x-add-version
* [liblsl] Update to 1.14.0
* Adjust CI baseline, assuming liblsl:x64-linux and liblsl:x64-osx pass
* Add back set(VCPKG_LIBRARY_LINKAGE dynamic)
* [libsls] Improve portfile.cmake, add homepage
* update version record
* Update ports/liblsl/CONTROL
* Update versions/l-/liblsl.json
* [liblsl] Use pugixml vcpkg package instead of bundled one
* Convert tabs to spaces
* Update version
* Fix Supports in liblsl/CONTROL
Co-authored-by: Robert Schumacher <roschuma@microsoft.com>
* Update versions/l-/liblsl.json
Co-authored-by: JackBoosY <yuzaiyang@beyondsoft.com>
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
Co-authored-by: Robert Schumacher <roschuma@microsoft.com>
* [mongoose] update to 7.1
* update version
* update suggested change
* update version
* delete Repeated version
* delete repeated version
* update version
* Don't copy svm-toy if not on Windows
svm-toy is only compiled on Windows, so should only be copied on Windows.
* Bump port version on libsvm. Switch to new manifest file format.
* [libsvm] Format manifest
* update version record
Co-authored-by: JackBoosY <yuzaiyang@beyondsoft.com>
The subject ("Your commitment") here is singular (IIUC).
I thought this worth fixing as it's one of first things many folks
will read about the project.
* [wil] Updating WIL version to match its nuget package version
* Removing port version from CONTROL file
* Revert "Removing port version from CONTROL file"
Reverting because PR tests are failing.
This reverts commit 28ffcba04b.
* Updating baseline.json and w-/wil.json
* update version
* modify portfile.cmake
* update version
Co-authored-by: Anand Arumugam <anand.arumug@gmail.com>
Co-authored-by: Anand Arumugam <anaaru@microsoft.com>
Co-authored-by: Jonliu1993 <13720414433@163.com>
* Copy over proj.pdb file on install
* Update port-version of proj4
* update version record
* Update proj4 version
* Update versions/p-/proj4
Co-authored-by: JackBoosY <yuzaiyang@beyondsoft.com>
* [vcpkg_*_cmake] remove deprecation message
to be replaced by a note in the maintainer-guide
this allows existing ports to build without warnings, so as to avoid warning people unnecessarily,
while still making sure people update when they update ports.
* Update docs/maintainers/maintainer-guide.md
* SObjectizer updated to v.5.7.2.3.
* New ver of SObjectizer added to versions list.
* Change 'version-string' to 'version'.
* Update for sobjectizer version in versions list.
