I think you misunderstood (or I didn't explain well),
so the concept was that Harbour zlib wrappers went
to _hbrtl_, all minizip functionality (and only that)
went to hbmzip, and we have hbzlib in core, which BTW,
you can choose to not use at all, by simply replacing
it with 'zlib1.lib' or your ow
Hi Mindaugas,
sounds a little complicated, but I have nothing better to suggest.
Just a wish for the future, I'd like to have possibility to use
zlib1.lib (import library created from zlib1.dll) instead of
hbzlib.lib.
The problem is we have to libraries:
1) zlib wrapper functions;
2) zlib
The core lib's name would naturally be hbzlib
(like hbpcre), but we already have hbzlib in
contrib, which collides with it.
So, I'd suggest to move strict zlib interface
functions (Harbour level ones that is) from
contrib/hbzlib to source/rtl, and rename the
remaining MiniZip stuff in contrib to
On Wed, 28 May 2008, Szakáts Viktor wrote:
Hi Viktor,
> Przemek had sent to me the zlib sources tamed
> for Harbour core, so I'm ready to upload them.
> There is one question though.
> The core lib's name would naturally be hbzlib
> (like hbpcre), but we already have hbzlib in
> contrib, which co
Hi all,
Przemek had sent to me the zlib sources tamed
for Harbour core, so I'm ready to upload them.
There is one question though.
The core lib's name would naturally be hbzlib
(like hbpcre), but we already have hbzlib in
contrib, which collides with it.
So, I'd suggest to move strict zlib int
