[MPlayer-dev-eng] libao2 usage in other projects

D Richard Felker III dalias at aerifal.cx
Tue Dec 30 04:08:55 CET 2003

On Tue, Dec 30, 2003 at 03:39:27AM +0100, Enrico Weigelt wrote:
> * Attila Kinali <attila at kinali.ch> [2003-12-29 19:03:04 +0100]:
> <snip>
> > > Well, aren't we here at the point where it becomes useful for splitting
> > > off libao2 to a separate package ? (see other thread on common api)
> > 
> > 1) Performance
> Sorry, I cant really understand this. What has performance to do w/
> external libraries. (this does not necessarily mean using shared libraries)

There are perforance penalties for making calls into shared libraries.

> > 2) We dont like external libs for things that should be done
> > inside the player itself
> What's the point, if this library is maintained by mplayer folks and
> provide mplayer's ilbao2 interface ?

You're asking the wrong question. The better questions is why we
should support using an "external" libao2 if we're the ones writing
it. There is no good answer.

> If you fear 'bad influence' from other projects, you can still ship a
> own branch w/ mplayer, which may be replaced by the 'open' branch 
> at build time. (i.e. --with-openao=...)

This is useless added complexity.


More information about the MPlayer-dev-eng mailing list