[MPlayer-dev-eng] release... WHEN?

[Arpi]

Hi,

> > anyway the project is already split to parts:
> > - libao2
> > - libvo
> > - libmpcodecs
> > - libmpdemux
> > - libmpdvdkit
> > - libavcodec (not even developed in mphq cvs, yet...)
> > - liba52
> > - libmpeg2
> > - input
> > - mplayer/mencoder core
> 
> Not that much split: most parts are very interdependant.  I mean you
not so much...

> can't really use libmpcodecs without bringing in nearly everything
> else, can you?
you can.
actually, libmpcodecs is a set of wrappers around internal (like libmpeg2,
native codecs, win32 interfaces) and external (divx4linux, vorbis etc) codec
APIs. so it's naturaly depends on them, but you can disable/remove the ones
you don't need so the left will work.
afaik libmpcodecs only depends on libmpdemux - but imho it's natural, there
is a way too deep data interchange between codecs and demuxers.

libmpdemux now compiles as-is, just do 'make test' in libmpdemux dir,
you'll get a small app able to open any movie file and print the basic file
info or even dump the streams.

libmpdvdkit did never depend on other parts.
the same is trye for libmpeg2, liba52, libavcodec and the other codecs libs.

dunno about libao2, libvo, i never to compile them independently from other
code, but i don't remember any deep dependancy.

also note, that some trivial dependency exists, like config.h, bswap.h, cpu
detection code and such, but they are easy to workaround if you plan to use
these libs for other projects.


A'rpi / Astral & ESP-team

--
Developer of MPlayer, the Movie Player for Linux - http://www.MPlayerHQ.hu