| commit | 946d3a086cc1736538c2d195bf4d8f564a51f4b4 | |
| author | Uoti Urpala <uau@glyph.nonexistent.invalid> | |
| Wed, 4 Nov 2009 04:16:47 +0000 (4 06:16 +0200) | ||
| committer | Uoti Urpala <uau@glyph.nonexistent.invalid> | |
| Wed, 4 Nov 2009 04:28:15 +0000 (4 06:28 +0200) | ||
| tree | b7d950bfdace498c4909f0973e5160a6fe465b8a | treesnapshot (tar.gz zip) |
| parent | cc96d177803b1ea01b489c2f5e211b40f39f133a | commitdiff |
Add --disable-vaapi to default FFmpeg configure flags
VA API support is useless for MPlayer, and trying to compile it (when
it was automatically enabled by FFmpeg configure) reportedly caused a
compilation failure in one case. So explicitly disabling it should
cause no harm but should help in some cases. Most likely the failing
system had a VA API header version installed that triggered support in
FFmpeg configure but didn't match FFmpeg source requirements.
VA API support is useless for MPlayer, and trying to compile it (when
it was automatically enabled by FFmpeg configure) reportedly caused a
compilation failure in one case. So explicitly disabling it should
cause no harm but should help in some cases. Most likely the failing
system had a VA API header version installed that triggered support in
FFmpeg configure but didn't match FFmpeg source requirements.
| script/ffmpeg-config | diffblobblamehistory |