* [libp7client, libp7-baical] Combine identical ports and update to libp7client 5.6.
In a recent CI build, we started getting output like:
Installing package libp7-baical[core]:x86-windows...
The following files are already installed in C:/Dev/vcpkg/installed/x86-windows and are in conflict with libp7-baical:x86-windows
Installed by libp7client:x86-windows
bin/P7x32.dll
bin/P7x32.pdb
debug/bin/P7x32d.dll
debug/bin/P7x32d.pdb
include/P7/GTypes.h
include/P7/P7_Client.h
include/P7/P7_Cproxy.h
include/P7/P7_Extensions.h
include/P7/P7_Telemetry.h
include/P7/P7_Trace.h
It turns out that these ports are identical, they are just different versions of the same library. The libp7-baical version supported more platforms and was simpler, so took that one and updated it to a current version.
* [ignition-modularscripts, ignition-msgs1] Attempt to fix intermittent build failures by disabling parallel configure.
* Fix several "passing: remove from fail list."
* [akali] Disable parallel configure.
REGRESSION: akali:x64-windows. If expected, add akali:x64-windows=fail to .\scripts\ci.baseline.txt.
Attempts to fix:
CMake Error: Could not open file for write in copy operation C:/Dev/vcpkg/buildtrees/akali/src/fc94eb83a9-01654d3f7c.clean/include/akali_config.h.tmp
CMake Error: : System Error: Permission denied
CMake Error at CMakeLists.txt:20 (configure_file):
configure_file Problem configuring file
* [nvtt] Devendor libsquish
This was regressed by https://github.com/microsoft/vcpkg/pull/13674
REGRESSION: nvtt:x64-linux. If expected, add nvtt:x64-linux=fail to .\scripts\ci.baseline.txt.
REGRESSION: nvtt:x64-osx. If expected, add nvtt:x64-osx=fail to .\scripts\ci.baseline.txt.
REGRESSION: nvtt:x64-windows-static. If expected, add nvtt:x64-windows-static=fail to .\scripts\ci.baseline.txt.
REGRESSION: nvtt:x64-windows. If expected, add nvtt:x64-windows=fail to .\scripts\ci.baseline.txt.
Installing package nvtt[core]:x64-linux...
The following files are already installed in /mnt/vcpkg-ci/installed/x64-linux and are in conflict with nvtt:x64-linux
Installed by libsquish:x64-linux
debug/lib/libsquishd.a
include/squish.h
lib/libsquish.a
* [knet] Disable parallel configure.
REGRESSION: knet:x64-windows. If expected, add knet:x64-windows=fail to .\scripts\ci.baseline.txt.
CMake Error at src/CMakeLists.txt:1 (configure_file):
configure_file Problem configuring file
* [libnice] Diable parallel configure.
REGRESSION: libnice:x64-windows. If expected, add libnice:x64-windows=fail to .\scripts\ci.baseline.txt.
CMake Error at CMakeLists.txt:13 (configure_file):
configure_file Problem configuring file
* [portaudio] Remove from baseline, fix CRT linkage and mark UWP as unsupported.
portaudio was fixed by 654adc64b3
* [chakracore] Remove passing case from baseline and add Supports.
PASSING, REMOVE FROM FAIL LIST: chakracore:arm64-windows (.\scripts\ci.baseline.txt)
* [gamma] Remove from baseline.
PASSING, REMOVE FROM FAIL LIST: gamma:x64-linux (.\scripts\ci.baseline.txt)
This was blocked by portaudio before.
* [usrsctp] Remove baseline
PASSING, REMOVE FROM FAIL LIST: usrsctp:arm-uwp (.\scripts\ci.baseline.txt)
PASSING, REMOVE FROM FAIL LIST: usrsctp:x64-uwp (.\scripts\ci.baseline.txt)
Probably fixed by 16b68c2f35
* [libopenmpt] Fix build on recent msvc by backporting deaf2e3837fb08b1a53fd21bb53adbafe0a84e7d
deaf2e3837
* [chakracore] Also needs dynamic universe.
* fix LLVM target-all feature
* [halide] bump Halide to version 10.0.0
* Use empty package policy to allow plugins to be located in lib.
This is following the recommendations in a conversation I had
with Robert Schumacher on the #vcpkg CppLang Slack channel.
This recommendation was derived from the fact that "cmake
defaults module DLLs into the lib folder, which makes vcpkg's
current policy very inconvenient for authors" and that I do not
plan to enable build systems other than CMake.
* [halide] skip x86-windows due to MSVC bug
* [halide] restore x64-windows-static fail status
* add usage file to Halide
* Update CONTROL version
* Remove '!emscripten` from ports/halide/CONTROL
Co-authored-by: NancyLi1013 <46708020+NancyLi1013@users.noreply.github.com>
Co-authored-by: Lily <47812810+LilyWangL@users.noreply.github.com>
Co-authored-by: NancyLi1013 <46708020+NancyLi1013@users.noreply.github.com>
* [log4cxx] Upgrade to newly released 0.11.0
* [log4cxx] 0.11.0 should build everywhere except uwp
* Changes suggested by @ras0219
* Prevent WIN32 libraries being used on linux
* Prevent WIN32 libraries being used on linux
* Prevent WIN32 libraries being used on linux
* Update ports/log4cxx/portfile.cmake
Co-authored-by: Stephen Webb <stephen.webb@sabreautonomous.com.au>
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
* [vcpkg osx ci] update to newer bits
these ones should actually work!
* update vagrantfile
* correct scripts, reformat, add docs
* Finish Get-InternalBaseBox, move archives
In order to avoid people maliciously deleting the boxes,
the archives share and file share are in different users now.
* baseline libqcow to be fixed later
* actually check for the mount point
* fix Install-Prerequisites again
* add +x to Get-InternalBaseBox.ps1
additionally, fix some errors
* Add static linking to Scintilla
* Add Port-Version to CONTROL
* Split library linkage from crt linkage
* Update CI baseline
* Remove vcpkg_copy_pdbs()
* [Many ports] Update to the latest version or commit
* [libplist] Update version
[libsync] Update patch format
* Update as review suggestions
* [libplist] Revert changes
* [xtensor-io] Disable undeclared HighFive detection which is currently broken.
HIGHFIVE 2.2.2: (Re)Detecting Highfive dependencies (HIGHFIVE_USE_INSTALL_DEPS=NO)
CMake Error: install(EXPORT "xtensor-io-targets" ...) includes target "xtensor-io" which requires target "libdeps" that is not in any export set.
CMake Error in CMakeLists.txt:
export called with target "xtensor-io" which requires target "libdeps" that
is not in any export set.
* [tcl] [taskflow] Mark passing in CI.
* Disable fluidlite in CI.
Fluidlite, added 3 days ago in https://github.com/microsoft/vcpkg/pull/13006 , tries to install the same files as fluidsynth; it's similar to the 'boringssl' situation. Given that fluidlite doens't have any dependencies, this change disables that one rather than fluidsynth,
* Add warning message.
