[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zlib-devel
Subject:    [Zlib-devel] [whisper] rather than libtool, what about a pkgconfig descriptor?
From:       jerker.back () telia ! com (=?iso-8859-1?Q?Jerker_B=E4ck?=)
Date:       2006-05-05 15:03:50
Message-ID: 004701c67055$1deadc60$0700a8c0 () syrenet ! home
[Download RAW message or body]

> sorry - I really meant to put this off given the current noise I've
generated, 
> but this has nothing to do with M$.
Noise on

Not exactly a reply and maybe just to make things even more compicated:
I'm building zlib with the Windows DDK utility build.exe
It's easy to maintain with a simple makefile/sources file
The result is a highly optimized Windows DLL depended only on the "system"
msvcrt with a perfect import library - this is the exact tool MS is using
when buildning their SDKs.
For example you got things like: /safeseh /pdbcompress /delay:unload and the
prefast test
The BufferOverFlowU.lib is also automatically linked in.
Tools version in current DDK (Windows DDK 2003 SP1): 7.1/13.10 4035

Even if I sympathies and find the manifest compile highly interesting, I
think it is really preferable to use the system msvcrt in a library as zlib.

Cheers Jerker




[prev in list] [next in list] [prev in thread] [next in thread]