Re: [Adonthell-devel] New zlib.dll that still doesn't work

[Kai Sterker]

On 11 Apr 2002 23:08:20 +0200 Alexandre Courbot wrote:

> Just have a doubt about your:
> > As for your
> > wintest2, I don't get any output, and I was too lazy to change the
> > code so the output goes into a file. (I tried from 11:00 to 17:00 to
> > fix that
> 
> Don't forget that under Windows nothing is outputed to the console (as
> there are aren't consoles!). Instead, the output is written in the
> stdout.txt and stderr.txt files. I think you already know this but
> what you said (redirecting into a file, while it already writes into a
> file!) makes me doubt! :)

Hm. I think the stdout and stderr text is something SDL does. But your
new test did not use SDL. OTOH, you can compile console apps under
windows that do output to the console (i.e DOS box or NT console). Of
course, we want a graphical app, so that's out of question. Besides, I
wouldn't know how to do it with cygwin. (That's really offtopic though.)


> > like to know whether the last two apps are working - these are the
> > only ones I was able to test with Wine (as the other can't init the
> > display). Both worked with Wine. I highly suspect DLL
> > incompatibilities anyway - as with one DLL and Wine and fails, and
> > another DLL works.
> 
> ...as with one DLL and Wine it fails, and with another DLL it works
> (under Wine, that is)

Hm. Wine isn't Win95, but one would imagine that something that runs
under Wine runs under Windows as well :P. Actually, I'm playing with the
thought of installing VC++ once again, and certainly some sort of email
client, so I don't need to reboot every other minute and do some
extented testing tomorrow.

Anyway, while it's possible that there are problems with the z.dll, the
versions I compiled myself where linked to a static libz that I compiled
myself as well. And the tests and minigzip I compiled myself worked fine
too. With cygwin!


> I just hope I'm not responsible for the Python mess, am I? You are
> working on the main branch anyway, right?

Right. I caused them somehow. It's very odd. It starts with the import
of the random module failing that is used in nearly all scripts. And the
reason for the failure are some sanity tests that go wrong. (See the
attached file and possibly the random.py module.) I expect that it is
somehow related to i18n, as that were the only changes I made to the
code. But I was more concerned getting the dialogue stuff to function
properly and haven't done anything about the python stuff yet. It's just
annoying. But well, I spent the afternoon and evening with a good book,
and hope to have some fresh ideas tomorrow :).

Kai

py_error.txt
Description: Text document