Mercurial > mplayer.hg
changeset 19899:b748e4e64b50
Allow shared libavcodec, but explain the implications.
| author | rathann |
|---|---|
| date | Tue, 19 Sep 2006 00:08:18 +0000 |
| parents | d77040154bad |
| children | eccf441ab9ff |
| files | DOCS/tech/binary-packaging.txt |
| diffstat | 1 files changed, 5 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/DOCS/tech/binary-packaging.txt Mon Sep 18 23:42:50 2006 +0000 +++ b/DOCS/tech/binary-packaging.txt Tue Sep 19 00:08:18 2006 +0000 @@ -83,12 +83,12 @@ package management system does not provide specific support for internationalization. -Libavcodec MUST always be in the latest development version and it MUST +Libavcodec MUST always be in the latest development version and it SHOULD be linked statically into the mplayer binary, because MPlayer requires a -recent libavcodec snapshot. While some distributions provide FFmpeg -packages containing a shared libavcodec library, they are often based on the -last "release" version of FFmpeg, which is quite old and will usually not -function correctly with MPlayer. +recent libavcodec snapshot. It is acceptable to use a shared (again, recent) +version of libavcodec, but you must be aware that this disables some of +MPlayer's functions (for example, some postprocessing filters) and sacrifices +speed. Support for binary codecs SHOULD be present to the extent that the combination of operating system and CPU architecture permits, but it MUST NOT result in a