OK, this would simplify things.fingolfin wrote: We do not use the C++ standard libraries at all, for portability reasons. Also, we already provide custom file system, savefile and "input file" handling APIs, as many platforms have problems with those. (Right now, our File API still requires fopen, though -- but this is going to change, too).
fopen, fread, fseek etc are supported by Cibyl, so it's probably easiest to use those - the reason I had to implement it a bit differently in Sarien (with the archive files loaded to memory -- still using the same file operations in the code) is to avoid having to answer "Allow reading a file?" dialogues all the time (and some performance advantages).
If someone decides to look at this I would suggest starting with disabling all engines except one of the smallest and continue from there. I would also disable things such as sound (which I guess can use some "null driver").
// Simon