madler
Where can I find the file zlib-1.2.11-win32-x86.zip?
The readme file for the Win32 version of ZLib (found here https://github.com/madler/zlib/blob/master/win32/README-WIN32.txt) makes reference to some zip file called zlib-1.2.11-win32-x86.zip which supposedly contains an already compiled copy of ZLib (including the DLL and import library as well as static library). Yet it doesn't say where to find this zip file. No direct download link to the file is mentioned, or even to a download page where several such files may be found. In fact, when I Google search for it, the search results all just point back to that one readme text file. No results show that the zip file itself even exists. Can somebody here let me know where to find that zip file?
I guess you have to compile it yourself. It's not so hard.
The documentation CLAIMS that a pre-compiled copy already exists, so it SHOULD exist. Please compile it for me. I want the latest version of the ZLib DLL.
Not so much a solution, but a prebuild zlib1.dll version 1.2.11 can be found in the SDL2_ttf runtime download: https://www.libsdl.org/projects/SDL_ttf/release/SDL2_ttf-2.0.15-win32-x64.zip
@madler I also do not have a Windows machine, but couldn't you build it using MinGW, in fact that is where I need this for :)
I don't have a Windows machine.
Then why does the documentation claim that a ZIP file exists with this DLL in it? Was that part of the readme file contributed by somebody else? Somebody else who planned to release the DLL but didn't follow through with it? If so, this discrepency should be resolved. I would prefer it if it were resolved by you compiling the DLL, but if you can't, then you should remove that part of the documentation to avoid misleading others to believe that you did compile such a DLL.
Also, even if you have a Linux machine, you can use a technique called cross-compiling to make the Windows DLL. You don't actually need a Windows machine to compile a Windows DLL.
That text was written 10 years ago, a lot can change in that time, it has for me :shrug:
I don't think your aggressive attitude is going to help further this, and your aren't saying anything that hasn't already been pointed out.
In case what you need was not a 64bit build, but a 32bit build then you can find that here. https://www.libsdl.org/projects/SDL_ttf/release/SDL2_ttf-2.0.15-win32-x86.zip
That text was written 10 years ago, a lot can change in that time, it has for me 🤷
I don't think your aggressive attitude is going to help further this, and your aren't saying anything that hasn't already been pointed out.
In case what you need was not a 64bit build, but a 32bit build then you can find that here. https://www.libsdl.org/projects/SDL_ttf/release/SDL2_ttf-2.0.15-win32-x86.zip
Sorry. I didn't mean to seem aggressive. I thought I was just pointing out a couple solutions to the situation. Cross compile for Windows, or remove that text from the readme. I didn't know I sounded angry. Sorry about that.
I don't know if that version of ZLib in that zip file is an unaltered version though, or if it has been modified for use with the SDL2 project. I don't know if it has dependencies on other files in the SDL2 project. If I'm using it for my project, and that project doesn't use other SDL features, I don't want to be tied to a version of ZLib that requires an additional DLL that I won't even be using.
To the best of my knowlage it is unmodified ad you will very quickly know if it has any further dependencies.
@madler I know of a perfect solution to that, setup, it should be simple to setup github actions and have it deploy the zip files then the problem should go away,
Also Note: I might make a v17 folder for the Visual Studio contrib folder (Visual Studio 2022) that will contain the following build targets:
- ia64 (if possible)
- x86
- x64
- arm
- arm64
Why arm you ask? Well this is because I have made a library in .NET that depends on this because the zlib provided by default in their runtime was poorly designed to where it won't let me access all of the functionality that the native zlib has.
Are warning messages during the compiling process normal? I got the dll successfully built, but the log was full of warning messages and I don't know whether everything is alright inside the .dll. An official build would be always nice while Mark Adler would do it within 5 minutes. I don't understand why source code developers always fear to release pre-compiled builds.
Will zlib ever get an update 1.2.12 or maybe 2.0 ?
I don't understand why source code developers always fear to release pre-compiled builds.
It's probably not fear but constraints. You could probably step up to be the Windows maintainer for the project and then do the pre-compiled releases for the platform.
Will zlib ever get an update 1.2.12 or maybe 2.0 ?
This feels like an off-topic question. The fact that it hasn't been created is probably another good indication that the developers working on the project are strained for resources. As fare as I can tell this project is largely being maintained by volunteers which means that any work being done on it is coming out of someones spare time.
Actually it is fear. The fear of owning and then having to figure out how the hell to use a Windows machine.
Actually, Windows is a lot easier than linux.
Why? because for Windows you do not have to worry about kali linux specific builds, ubuntu specific builds, rhel specific builds of zlib, just x86, x64, ARM (Up to Windows 10), and ARM64 specific builds.
@AraHaan maybe take the Windows vs Linux debate one Reddit or somewhere else where you don't ping people with an email