2008/12/19 <dg...@ni...>:
> Have we altered this copy of zlib in any way
> that triggers these requirements? If so, has
> anyone already taken the required steps to
> prepare for re-distribution of the altered
> source code?
So far, everything is unaltered. However on win32
there is a problem that two neccessary functions
are missing from the dll export. Therefore I
submitted this problem, but didn't receive an
answer yet. Yesterday I registered to be a
zlib developer, so I could contribute this
change (however small) to zlib.
> Should the tcl/compat/zlib directory that we
> distribute include the "license.terms" file
> that goes in (all?) other directories of a
> Tcl source code distribution?
I don't know, but I'll take that up with Mark
Adler and check in the necessary changes.
Below the mail I received from him and my answer.
I'm interested in this because tkImg could
in time use the same zlib1.dll that Tcl
is using. And if people download a new
zlib1.dll from zlib.net (1.2.4, with those
fixes, hopefully) they should not have to
wait for a new Tcl build to make use of it,
just replace the dll.
Regards,
Jan Nijtmans
2008/12/18 Jan Nijtmans <nij...@us...>:
> 2008/12/18 Mark Adler <ma...@al...>:
>> Hi,
>>
>> Before I sign you up, please let me know how you can contribute to the
>> testing of new versions of zlib. Thanks for your offer to help.
>
> Starting with version 8.6, zlib will be standard part of Tcl/Tk. See:
> <http://www.tcl.tk/cgi-bin/tct/tip/234.html>
> Therefore, zlib 1.2.3 has been imported in the Tcl repository
> in sourceforge.
>
> I am currently working in getting everything to build under Windows
> (both msvc and mingw), when I discovered that two symbols were
> missing from win32/zlib.def. I mailed you about that, but didn't
> receive a reaction yet. However, we will try to integrate zlib's
> build into Tcl's build, that's why I'm interested to follow the
> current developments of zlib, and test the build in combination
> with Tcl.
>
> Regards,
> Jan Nijtmans
|
