Revisiting MPlayers PostProcessing filter

Randy McMurchy randy at linuxfromscratch.org
Fri Dec 24 11:40:19 PST 2004


Hi all,

Merry Christmas!

Here is a bug which prompted a change to the MPlayer instructions
to pull out the creation and installation of the shared postprocessing
library:

==============Begin Bug================
http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=1049

            Summary: --enable-shared-pp should not be used.
            Product: Beyond LinuxFromScratch
            Version: SVN
           Platform: PC
                URL: http://lfs.netservice-
                     neuss.de/blfs/view/svn/multimedia/mplayer.html
         OS/Version: Linux
             Status: NEW
           Severity: minor
           Priority: P2
          Component: BOOK
         AssignedTo: blfs-book at linuxfromscratch.org
         ReportedBy: Reimar.Doeffinger at stud.uni-karlsruhe.de
          QAContact: blfs-book at linuxfromscratch.org


I think there was a misunderstanding as to what --enable-shared-pp does. It just
makes MPlayer compile and link to the postprocessing library dynamically instead
of statically. The functionality will always be compiled in. As dynamic linking
often causes problems, this switch should not be used.
Also, it is recommended to install all codecs always into /usr/lib/codecs.
Like this, it will also be recognized automatically and MPlayer will compile
with codecs support, the --with-codecsdir is not necessary in that case.
Would be nice if you could do these changes.
==============End Bug================

I think users should be made aware of MPlayer's shared postprocessing
library, mainly because it is looked for by other packages (transcode,
FFDShow and others). Now I don't necessarily agree with the statement
above "dynamic linking often causes problems", especially with MPlayer's
postprocessing library. But I digress....

I am updating BLFS to MPlayer-1.0pre6 and think that maybe I should put
a blurb in the instructions that passing --enable-shared-pp is necessary
to build the shared library, and then put optional instructions to build
and install the library.

What say the group?

-- 
Randy



More information about the blfs-dev mailing list