[MPlayer-dev-eng] [PATCH] don't link mplayer with encoding libsand allow disabling some encoders in lavc
Dominik 'Rathann' Mierzejewski
dominik at rangers.eu.org
Thu Nov 9 23:14:14 CET 2006
On Thursday, 09 November 2006 at 00:07, Rich Felker wrote:
> On Wed, Nov 08, 2006 at 09:55:10PM +0100, Nico Sabbi wrote:
> > Reimar Döffinger wrote:
> >
> > >Hello,
> > >On Wed, Nov 08, 2006 at 09:57:46AM +0100, Nico Sabbi wrote:
> > >
> > >
> > >>All this mess wouldn't be necessary if we used only pkg-config (as for
> > >>lav[cf] external),
> > >>and configure would be much much cleaner.
> > >
> > >This assumes pkg-config works. Which on Linux systems is mostly but not
> > >always true, and on Solaris, Windows and FreeBSD usually is not at all
> > >the case.
> > >And a broken pkg-config leads to even more complicated problems because
> > >it is much harder to find out what is going on without direct access to
> > >the problematic PC.
> >
> > in this case a brand new ffmpeg-config seems to be the only viable
> > and cross-platform option, do you agree?
>
> No, this is nonsense. -lavc is all that's needed.
What if I'm linking to lavc statically?
> If the user
> installed it in a nonstandard location it's their responsibility to
> add the paths. foo-config scripts are an ABOMINATION because they
> break cross-compiling and cause all other sorts of nightmares for
> people not using the 'standard' linux setup.
It's not about location. It's about what addtitional libraries lavc was
linked with.
Regards,
R.
--
MPlayer developer and RPMs maintainer: http://rpm.greysector.net/mplayer/
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
More information about the MPlayer-dev-eng
mailing list