As in case with mui-owb, i just start some thread where will post all the info about current progress and put all the info.
So, in brief, we have build with Deniil today AROS-version of mplayer (thanks to Deadwood who help with boring with aros-specific configure-files) which just the version from 11.11.2010 (i.e. 1.5 years old) from Fab (I.e. deadwood 1.5 year ago just port fab's version at this time)
Why we not port latest fab's version which just few months old ? We port it, but start to have some strange problems, which point us out on some random memory trashing, we spend 2 days with Deniil to understand it, i annoy fab a lot (like i the first days with muiowb). Crashes was random, stacktrace was broken (i.e. no stacktrace) , everything points on some strange "68k cross calls".
For example at running we have NULL for some objects, on other run are not. If we comment one part or another, its just randomly reacts. So, i think better to start from AROS port (just to be sure, that we not mess something in porting code), and just to know, will AROS port have the same problem on aos4 after porting, or not.
So, with help of deadwood, we build today aros version, and, how sadly it was : bugs was the same.
Then we remove all optimisation, add debugging info , and so, stack-trace start to be more or less fine, and we found, that roots of the problem was : sucking DoSuperNew (about which fab say to me yesterday).
But what is was a bit suprising, is that i already add on linking stage our aos4deps.a library , which we use for MUIOWB, which, have inside DoSuperNew.
The problem was because of we do not declare any prototype for DoSuperNew in the sources of mplayer , and so, compiler by default just make it as INT , and throug all params over stack, while our one are :
Object * VARAGS68k DoSuperNew(blablalblab)
Without that proto, linker by default make it as INT, and then, even if we have "right" DoSuperNew in the aos4deps.a , it was ####ed, and in end all possible random erros and crashes.
And end of all , we have port of mui-mplyaer which 1.5 years old, and reported from AROS, here is 2 screenshots:
http://kas1e.narod.ru/mplayer/mplayer_first_try.jpghttp://kas1e.narod.ru/mplayer/mplayer_first_try2.jpgWhat we will do in terms of mplayer for now:
Compile latests Fab's code and fix all the bugs in the mplayer itself. If there will be some problems, then will fix 1.5years old port from aros, fix some small bugs (a very small ones) and realease.