You must be logged in to post

Game Development Community

Filter Filter

Updated zlib (Security Fix)

by James Lupiani · 08/12/2005 (4:01 pm) · 6 comments

Download Code File

There were some added/removed files for this version, so your best bet to updating this is to clear out everything under \engine\lib\zlib. Then decompress the zip file in that directory.

In Visual Studio (or your makefile, project, whatever), remove all the previous zlib files. Right-click on the zlib project, add existing files, and select the files you just extracted to the zlib directory.

Clean, build, enjoy.
NextNext resource
PrevPrevious resource
More resources


Associate Ben Garney
#1
08/12/2005 (4:01 pm)
1.4 has all of its support libraries (including this one) updated to the latest stable version. Thanks for posting this fix (and reminding me to do that), James!

Torque Owner Mark Kromis
Default Studio Name
#2
08/13/2005 (2:15 am)
Since linux and Mac has this as system wide libraries, would it be wise to link ageist them and let the system handle the update? This way when there is a new update, the engine would get it automatically. Opinions?

BTW Does windows have a system wide zlib.dll file?

Associate Ben Garney
#3
08/13/2005 (2:32 am)
Thanks for your thoughts. In fact, I already had a discussion very similar to this with Paul earlier yesterday, and will continue to explore possibilities up until the time 1.4 ships. It looks like for mac and linux we will try to use system libs, and on windows, use a local instance of the codebase.

Torque 3D Owner Steve Kilcollins
Imagination U
#4
08/13/2005 (6:50 am)
Can't download the file, when click on the zlib_123 link, it just reposts the page

Associate James Lupiani
Sickhead Games
#5
08/13/2005 (2:23 pm)
Re-uploaded it, seems to work now.

Torque Owner Gregory "Centove" McLean
#6
08/15/2005 (3:04 pm)
@Ben,

I can confirm on linux it does
libz.so.1 => /lib/libz.so.1 (0x41990000)

The lib in the engine directory is just used for compiling and linking the executable. When executing the resulting binary directly it will use the dynamic linker to resolve the library references.