Hi,

> Hello Arpi,
> 
> Thursday, October 25, 2001, 10:15:29 AM, you wrote:
> 
> A> as we don't allow creating binary packages of mplayer yet.
> 
> 
> Why is that?
> 

because mplayer is not ready for this.
most of optimization and feature are configured at compile-time.
so if you compiled (and configure script detected your cpu, lib versions,
kernel version etc) you won't be able to run that binary on different
system, as you'll get unresolved symbols, lib incompatibilty problems, and
of course big slowdown or illegal instruction ex.

we don't like dynamic libraries, and function pointers due to speed loss.
optimized cpu-dependnet stuff are #ifdef-ed, version-dependent stuff (for
example each SDL release has its own bug to be workarounded) are #ifdef-ed.

we'll change it but now we've things with higher priority.


A'rpi / Astral & ESP-team

--
mailto:[EMAIL PROTECTED]
http://esp-team.scene.hu

_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile

Reply via email to