[MPlayer-dev-eng] FFmpeg, svn:externals and where to go from here
siretart at tauware.de
Wed Jan 26 21:56:43 CET 2011
On Mi, Jan 26, 2011 at 19:17:31 (CET), Reimar Döffinger wrote:
> On Wed, Jan 26, 2011 at 07:33:59AM +0100, Reinhard Tartler wrote:
>> On Tue, Jan 25, 2011 at 22:32:29 (CET), Reimar Döffinger wrote:
>> >> This looks no harder than compiling both MPlayer and FFmpeg to me.
>> > Which is double the effort of just compiling MPlayer.
>> > However that is not counting the worst: either installing FFmpeg
>> > or beating it to be useable without installing.
>> What's the problem with installing FFmpeg on Windows? Seriously,
>> is there something that can done to make this step easier?
> Not Windows-specific really, except that there's not even the
> option of using a system one.
> The issues are
> - additional steps (yet another configure to run, with different
> options which is particularly annoying for cross-compiling)
> - non-trivial to start a compile of everything so you can go
> do something else (bigger issue on Linux actually due to
> make install since by default that needs root)
I feel both could be solved by some scripting, which we could include in
the mplayer sources
> - no reliable make uninstall
only if you insist on installing to /usr/local. I personally prefer to
> - pkg-config usually does not work, so (IIRC) you manually need to convince
> MPlayer to find it
Well, non-standard paths require adjustment to various environment
variables like PATH, LD_LIBRARY_PATH and PKG_CONFIG_PATH. But setting
environment variables is also no rocket science either, rather a matter
of writing that down properly.
> In general just try to make a list of the steps needed
> if you want a user to test a patch that changes both FFmpeg and MPlayer.
Reinhard Tartler, KeyID 945348A4
More information about the MPlayer-dev-eng