* [vtk] update to 9.0.1
* [paraview] silence linux ci by adding embree3 as a build-depends to paraview (just a workaround)
* [vtk] disable remote modules to make feature all actually work
* [vtk] delete old patch
--editable suppresses binary caching and source re-extraction for packages listed on the command line (similar to --head).
This fundamentally changes the port maintenance loop, so several example documents were updated. To avoid users having substantial changes suddenly destroyed by forgetting to pass --editable, "clean" sources have different extract locations.
The undocumented command `build` implies `--editable`.
Co-authored-by: Robert Schumacher <roschuma@microsoft.com>
* [getdns] Add new port.
* Add support for vcpkg static library builds.
* Convert libevent and libuv libraries to features.
* Use ${PORT} in copyright install.
* getdns does not currently support UWP.
* Add failing port on UWP to portfile.
* Remove optional FEATURES keyword.
* Update .gitignore
* Add mingw dynamic lib triplets
* Only copy pdbs if not using *-mingw triplets
* Using VCPKG_POLICY_DLLS_WITHOUT_LIBS as a workaround
* Rename *-mingw to *-mingw-dynamic
Co-authored-by: Billy Robert O'Neal <bion@microsoft.com>
* Add egl renderer to list of files compiled for linux
* Update Control File as per request from vcpkg reviewers
Co-authored-by: Ankur Verma <ankurv@localhost.localdomain>
* [libffi] Add pkgconfig file
- Configure and add the libffi.pc file.
- Furthermore, enable the check for same 32/64bit-ness in
libffiConfigVersion.cmake again, which had caused issues in the past
with newer versions of glib using meson build, e.g. when building for
x86-windows target on an x64-windows host.
Now, libffi is found by current glib (e.g. 2.64.3) during
meson build using the libffi pkgconfig file.
* Check VCPKG_BUILD_TYPE to handle release/debug
* Update tinyfiledialogs version and download path to v3.6.3
* update sha512 hash
* Fix download link having an extra version ref
* Fix filehash being uppercased
* again, fixed some ci.baseline errors
* Added python script to generate all packages file list, added to azure pipeline to build at the end of the run
* fixed an issue that causes some leading slashes were being removed
* Header Database now includes hpp files for C++ header files
* Changed Header Database to include all files under \include\ folder
* Apply suggestions from code review, changing condition from eq to ne
Co-authored-by: Billy O'Neal <bion@microsoft.com>
* Update last condition from eq to ne
Co-authored-by: Billy O'Neal <bion@microsoft.com>
* [libexif] Update to 0.6.22
From the release page on github:
> It largely contains stability, security and bugfixes.
>
> Some EXIF 2.3 tags have been added.
>
> It is ABI compatible to 0.6.21 release.
* [libexif] Fixes to portfile.cmake
- don't include vcpkg_commong_functions
- use the PORT variable when installing copyright file
* [libexif] Use vcpkg_fail_port_install
Co-authored-by: Oskari Timperi <oskari.timperi@novatron.fi>
* [ace] 6.5.10
* Add version macros to make the port file easier to update
* ports/ace/portfile.cmake:
* Updated macro names to have ACE_ prefix
* ports/ace/portfile.cmake:
* Use string replace
* ports/ace/portfile.cmake:
* Increment CONTROL file version
Increment CONTROL file version for mpg123 due to changes made to differentiate between library files being put in /lib64 instead of /lib on OpenSUSE 15.x linux
* Update portfile.cmake to differentiate between /lib64 and /lib libraries on OpenSUSE 15.x linux
Update portfile.cmake to differentiate between /lib64 and /lib libraries on OpenSUSE 15.x linux
* [pcre] Use vcpkg_from_sourceforge as a fallback
* Update ports/pcre/CONTROL
Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
Use IncludePath and LibraryPath propertiesThese tool agnostic properties allow to configure ClCompile and ResourceCompile without repeating the code.
This change includes my changes from #4454.
Co-authored-by: Nicole Mazzuca <mazzucan@outlook.com>
This changes our PR builds to treat 'fail' in the ci.baseline.txt as 'skip' instead of using tombstones.
We currently have large numbers of spurious failures that get enshrined in PRs through no fault of a PR author, removing the tombstones concept will fix those by allowing the user to retry. This does mean we accept some risk of not detecting when a port is 'fixed', but that failure is reasonable for us to handle after we see it in CI, but that seems worth it given that it lets us get rid of the tombstone concept.
This also helps out the binary caching feature, because we don't have to figure out how to productize tombstones.
