libav: libvpx >= 1.8 drops some formats #111172
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
The recent upgrade of libvpx to 1.8/1.9 broke libav_12.
The issue, as can seen above, is that some libvpx has dropped some of its previously supported formats. The effected code just converts VPX image format constants to AV image format constants, and the solution, as found in this patch here is to simply
#if
out the conversion lines for the dropped formats when building against the newer libvpx.This simply results in the case falling through to the default none format constants and follows the existing
#if
statements found in the code for differences in various other versions of libvpx.This pull request adds the referenced patch for libav_12. It is applied unconditionally to libav_12 as libvpx <= 1.7 (the ones that had the dropped formats) were removed with the libvpx upgrade that causes this issue.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)