Ffmpeg 2.1 #1610
Merged
Ffmpeg 2.1 #1610
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
deprecated: http://git.videolan.org/?p=ffmpeg.git;a=commit;h=0eea212943544d40f99b05571aa7159d78667154 broken with libavcodec 54
deprecated: http://git.videolan.org/?p=ffmpeg.git;a=commit;h=95510be8c35753da8f48062b28b65e7acdab965f broken with libavcodec 55
deprecated: http://git.videolan.org/?p=ffmpeg.git;a=commit;h=104e10fb426f903ba9157fdbfe30292d0e4c3d72 broken with libavcodec 55
|
Can one of the members verify this patch? |
|
@freerdp-bot test. |
|
Test PASSed. |
cocoon
pushed a commit
to cocoon/NeutrinoRDP
that referenced
this pull request
Mar 3, 2017
cocoon
pushed a commit
to cocoon/NeutrinoRDP
that referenced
this pull request
Mar 8, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #1385
With these changes, freerdp builds against ffmpeg-2.1 on Gentoo (current ~amd64 branch). The test suite passes, but I'm unsure if that excersises the ffmpeg interface. Build and tests are verified to not have broken against ffmpeg-1.2.4.
I am not sure how to properly verify runtime functionality, so please test carefully.