[Scummvm-devel] ScummVM 0.12.0

[John Willis]

Hi Chaps,

I am all for a 0.12.0 release, there is plenty in TRUNK to go over and the
timeline seems good for me (being selfish).

>Fine by me. However, this time, it would be nice if we could get the  
>ports ready a bit earlier, so that testing could be performed on  
>those, too...

Sounds like a very good idea, maybe we really need to move to pushing for
formal public RC port builds a min of 10 days before release? Thoughts?

I know I have fallen foul of getting final builds done in time but I tend to
do a series of RC style builds for my users and it has worked well in the
past for feedback. The RC builds are very different things to the usual
TRUNK builds people come to expect and are spread out a bit wider.

Some very specific timelines for release point stuff and a little 'prodding'
may not do any of us any harm ;-). 

>@Kostas: If you have *any* questions about the plugin code, or any of  
>the "intimidating" innards of ScummVM, never hesitate to ask. I'll be  
>happy to answer, and could even be convinced to write docs (at least  
>doxygen docs) for parts of the code, if you just tell me which part of  
>the code you need better documented (documenting all would be best,  
>but well, I can't do that on my own). That could include an overview  
>of how certain things interact... What do you need?

Ok, not Kostas here ;) but the increasing number of engines and size is
starting to become a bind on the GP2X for the same reasons as WinCE. 

My snag is that for a number of reasons we static link the GP2X builds
(ancient gLibC in firmware, that sort of thing) and I have never got a
working mashup of dynamic engine plugins and static everything else. 
I know we used to have problems in the past with things like SCUMM depending
on zLib etc. but even with them sorted I have never got a good build out of
the posix plugin setup (and a custom plugin setup seems wrong when we are
really just building for ARM Linux on the GP2X). As usual there is the risk
I am being terminally stupid and missing the obvious again mind you.

Regards,

John