<!-- If your PR fixes issues, please note that here by adding "Fixes
#NNNNNN." for each fixed issue on separate lines. -->
<!-- If you are still working on the PR, open it as a Draft:
https://github.blog/2019-02-14-introducing-draft-pull-requests/. -->
If this PR updates an existing port, please uncomment and fill out this
checklist:
- [X] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [X] SHA512s are updated for each updated download.
- [X] The "supports" clause reflects platforms that may be fixed by this
new version.
- [X] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [X] Any patches that are no longer applied are deleted from the port's
directory.
- [X] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [X] Only one version is added to each modified port's versions file.
<!-- If this PR adds a new port, please uncomment and fill out this
checklist:
- [ ] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] The name of the port matches an existing name for this component
on https://repology.org/ if possible, and/or is strongly associated with
that component on search engines.
- [ ] Optional dependencies are resolved in exactly one way. For
example, if the component is built with CMake, all `find_package` calls
are REQUIRED, are satisfied by `vcpkg.json`'s declared dependencies, or
disabled with
[CMAKE_DISABLE_FIND_PACKAGE_Xxx](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html).
- [ ] The versioning scheme in `vcpkg.json` matches what upstream says.
- [ ] The license declaration in `vcpkg.json` matches what upstream
says.
- [ ] The installed as the "copyright" file matches what upstream says.
- [ ] The source code of the component installed comes from an
authoritative source.
- [ ] The generated "usage text" is accurate. See
[adding-usage](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/examples/adding-usage.md)
for context.
- [ ] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [ ] Only one version is in the new port's versions file.
- [ ] Only one version is added to each modified port's versions file.
END OF NEW PORT CHECKLIST (delete this line) -->
* [amd-amf] Update to 1.4.29
* [ffnvcodec] Update to 11.1.5.2
* [mfx-dispatch] Fix pkgconfig
* [ffmpeg] Update to 6.0
* update versions
* [amd-amd] Fix merge
* Update ffmpeg.json
* ffmpeg: Remove libpng dependency.
Ffmpeg doesnt have a libpng dependency. All thats needed for png support is zlib which has its own option already
* Update ffmpeg.json
* [ignition-common3] patch for ffmpeg3
* [freerdp] Update to 2.11.1
* Revert "Merge pull request #1 from autoantwort/ffmpeg"
This reverts commit b52416c67dc8c0fd97365050513f2f4a47c631c4, reversing
changes made to 8fdd44e901184f051345220b22db89467c1c265a.
* Update ffmpeg.json
* Update ffmpeg.json
---------
Co-authored-by: Leander Schulten <Leander.Schulten@rwth-aachen.de>
* [ffmpeg] Fix off-by-one issue when looping over the OSX_ARCHS
This fixes crosscompiling e.g. arm64 on x64
* [ffmpeg] Remove redundant --enable-cross-compile flag
* [ffmpeg] Bump port version
* Update ffmpeg to 4.4.3
- Backport fix for h.264 hardware decoding on M1 macs
- ffmpeg links against built-in atomic, not a findable lib
* add missing extension for new patch
* version!
Co-authored-by: Martijn Otto <martijn@resolume.com>
Co-authored-by: Javier Matos Denizac <javier.matosd@gmail.com>
* [ffmpeg] Update the download address of gcc under windows arm
* Never gcc download under windows arm
* update ffmpeg.json
* Removed download requirement for "cpp.exe" preprocessor
* x-add-version
I tried to build FFmpeg for ARM64 but I got an error.
The problem happens because portfile.cmake uses gcc-9.3.0 but it has been removed from repository.
See:
https://repo.msys2.org/msys/x86_64/
So, it is just needed to update that file to the newer updated version and you will be able to build FFmpeg for ARM64 again.
* [ffmpeg] Set --disable-audiotoolbox when targeting iOS
* [ffmpeg] Bump port version to 19
* Update ffmpeg.json
Co-authored-by: Cheney Wang <38240633+Cheney-W@users.noreply.github.com>
* Fix failure of cross-compiling for ffmpeg due to use inappropriate strip.
* Update port version of ffmpeg.
* Remove redundant adjust condition.
* Update version database
Co-authored-by: Jamlys Lee <jamlys_lee@163.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>
* [ffmpeg] Update dependency support for recent changes.
Updates for changes in commits:
7bb175e [aom/libavif] Add support for ARM and UWP
a8204d9 [fribidi] Support new platform
* update
* [ffmpeg] update x264 supports.
* Fix version database.
* update
* Update all platform checks and error messages
* Update vcpkg.json
* Update ffmpeg.json
* fixup osx.
* another osx fixup
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
* [ffmpeg] fix cross compilation on mac arm64 to x86_64
* Bump port-version
* Bump port-version again.
Co-authored-by: Billy Robert ONeal III <bion@microsoft.com>
* [ffmpeg] do not pull in postproc for LGPL build
* [ffmpeg] disable avisynthplus on static builds (as it is not functional)
* [ffmpeg] bump port version
* [ffmpeg] x-add-version
