diff options
author | Yasha Jannoo <alledodo@gmail.com> | 2019-09-14 12:15:04 +0100 |
---|---|---|
committer | Yasha Jannoo <alledodo@gmail.com> | 2019-09-14 12:51:21 +0100 |
commit | f2e1338eba568ac7caa0051d57f1f6a10ae81801 (patch) | |
tree | 4a6589fb83fe95308b75a76505d97a972f2bd7be /zlib/contrib/vstudio/readme.txt | |
parent | e31b0c1803d976e29b258c7307e32fd0d63821e5 (diff) | |
download | starshatter-f2e1338eba568ac7caa0051d57f1f6a10ae81801.zip starshatter-f2e1338eba568ac7caa0051d57f1f6a10ae81801.tar.gz starshatter-f2e1338eba568ac7caa0051d57f1f6a10ae81801.tar.bz2 |
Update zlib 3rd party code to v1.2.11
zlib source code, version 1.2.11. https://www.zlib.net/.
Include all the gynmastics involved in:
- making sure we compile zlibstat and set the output files locations and filename to those expected by the starshatter setup.
- turning off the ASM includes as they are invalid for the new versions of zlib (and crash when running).
- matching the calling conventions of the Starshatter code by ommiting ZLIB_WINAPI from the zlib preprocessor defines.
- fix debug build compile error in zlibstatic:
https://stackoverflow.com/questions/31867018/unresolved-external-symbol-except-handler4-common-in-visual-studio-2015
This fixes some string warnings.
Diffstat (limited to 'zlib/contrib/vstudio/readme.txt')
-rw-r--r-- | zlib/contrib/vstudio/readme.txt | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/zlib/contrib/vstudio/readme.txt b/zlib/contrib/vstudio/readme.txt new file mode 100644 index 0000000..48cccc0 --- /dev/null +++ b/zlib/contrib/vstudio/readme.txt @@ -0,0 +1,78 @@ +Building instructions for the DLL versions of Zlib 1.2.11 +======================================================== + +This directory contains projects that build zlib and minizip using +Microsoft Visual C++ 9.0/10.0. + +You don't need to build these projects yourself. You can download the +binaries from: + http://www.winimage.com/zLibDll + +More information can be found at this site. + + + + + +Build instructions for Visual Studio 2008 (32 bits or 64 bits) +-------------------------------------------------------------- +- Decompress current zlib, including all contrib/* files +- Compile assembly code (with Visual Studio Command Prompt) by running: + bld_ml64.bat (in contrib\masmx64) + bld_ml32.bat (in contrib\masmx86) +- Open contrib\vstudio\vc9\zlibvc.sln with Microsoft Visual C++ 2008 +- Or run: vcbuild /rebuild contrib\vstudio\vc9\zlibvc.sln "Release|Win32" + +Build instructions for Visual Studio 2010 (32 bits or 64 bits) +-------------------------------------------------------------- +- Decompress current zlib, including all contrib/* files +- Open contrib\vstudio\vc10\zlibvc.sln with Microsoft Visual C++ 2010 + +Build instructions for Visual Studio 2012 (32 bits or 64 bits) +-------------------------------------------------------------- +- Decompress current zlib, including all contrib/* files +- Open contrib\vstudio\vc11\zlibvc.sln with Microsoft Visual C++ 2012 + +Build instructions for Visual Studio 2013 (32 bits or 64 bits) +-------------------------------------------------------------- +- Decompress current zlib, including all contrib/* files +- Open contrib\vstudio\vc12\zlibvc.sln with Microsoft Visual C++ 2013 + +Build instructions for Visual Studio 2015 (32 bits or 64 bits) +-------------------------------------------------------------- +- Decompress current zlib, including all contrib/* files +- Open contrib\vstudio\vc14\zlibvc.sln with Microsoft Visual C++ 2015 + + +Important +--------- +- To use zlibwapi.dll in your application, you must define the + macro ZLIB_WINAPI when compiling your application's source files. + + +Additional notes +---------------- +- This DLL, named zlibwapi.dll, is compatible to the old zlib.dll built + by Gilles Vollant from the zlib 1.1.x sources, and distributed at + http://www.winimage.com/zLibDll + It uses the WINAPI calling convention for the exported functions, and + includes the minizip functionality. If your application needs that + particular build of zlib.dll, you can rename zlibwapi.dll to zlib.dll. + +- The new DLL was renamed because there exist several incompatible + versions of zlib.dll on the Internet. + +- There is also an official DLL build of zlib, named zlib1.dll. This one + is exporting the functions using the CDECL convention. See the file + win32\DLL_FAQ.txt found in this zlib distribution. + +- There used to be a ZLIB_DLL macro in zlib 1.1.x, but now this symbol + has a slightly different effect. To avoid compatibility problems, do + not define it here. + + +Gilles Vollant +info@winimage.com + +Visual Studio 2013 and 2015 Projects from Sean Hunt +seandhunt_7@yahoo.com |