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 itself.
Both of them ties for the same name hbzlib. The proposed solution is
to move zlib wrapper functions to hbmzip (together with minizip
code). Putting zlib wrapper function into hbzlib could seem more
natural, but this choice will not allow to use dynamic library.
The other strange thing is that we have zlib in the core code, but
zlib wrapper functions in contrib. I would suggest to let developers
avoid contrib and move zlib wrapper functions to the core also.
Using the same hbzlib library is a bad choice (see above). One more
library for wrapper functions is not nice solution also. We can
create module containing wrapper functions in rtl library.
Thus:
rtl.lib + hbzlib.lib = static linked zlib functionality
rtl.lib + zlib1.lib = dynamically linked zlib functionality
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 own static build.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
