Hello, from the compilation log you can read:
[CC] lib\3rdparty\zlib\adler32.c [CC] lib\3rdparty\zlib\compress.c [CC] lib\3rdparty\zlib\crc32.c [CC] lib\3rdparty\zlib\gzio.c [CC] lib\3rdparty\zlib\uncompr.c [CC] lib\3rdparty\zlib\deflate.c [CC] lib\3rdparty\zlib\trees.c [CC] lib\3rdparty\zlib\zutil.c [CC] lib\3rdparty\zlib\inflate.c [CC] lib\3rdparty\zlib\infback.c [CC] lib\3rdparty\zlib\inftrees.c [CC] lib\3rdparty\zlib\inffast.c [AR] obj-i386\lib\3rdparty\zlib\zlib.a
why does it compile zlib.a (absolutely unuseful in my opinion) instead of zlib1.dll with its libz.a? This log has been taken from the compilation of ReactOS and *not* from the "make bootcd" session.
Sincerely,
Carlo Bramini.
------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-modeĀ di Wind http://i-mode.wind.it/
Hi it beaing use for extact and compress cab files and network trafic. zlib light compress program, that are been use for transfer data at network level, and cab files. it also being use in allot other area in windows. And it also being use in diffent font file to decompress bitmap and other data.
----- Original Message ----- From: "carlo.bramix" carlo.bramix@libero.it To: "ros-dev" ros-dev@reactos.org Sent: Tuesday, September 04, 2007 11:19 AM Subject: [ros-dev] Build with zlib
Hello, from the compilation log you can read:
[CC] lib\3rdparty\zlib\adler32.c [CC] lib\3rdparty\zlib\compress.c [CC] lib\3rdparty\zlib\crc32.c [CC] lib\3rdparty\zlib\gzio.c [CC] lib\3rdparty\zlib\uncompr.c [CC] lib\3rdparty\zlib\deflate.c [CC] lib\3rdparty\zlib\trees.c [CC] lib\3rdparty\zlib\zutil.c [CC] lib\3rdparty\zlib\inflate.c [CC] lib\3rdparty\zlib\infback.c [CC] lib\3rdparty\zlib\inftrees.c [CC] lib\3rdparty\zlib\inffast.c [AR] obj-i386\lib\3rdparty\zlib\zlib.a
why does it compile zlib.a (absolutely unuseful in my opinion) instead of zlib1.dll with its libz.a? This log has been taken from the compilation of ReactOS and *not* from the "make bootcd" session.
Sincerely,
Carlo Bramini.
------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-modeT di Wind http://i-mode.wind.it/
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Um, because it's a static library? Do you see it in the "dll" directory or in the "lib" directory?
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of carlo.bramix Sent: September-04-07 5:19 AM To: ros-dev Subject: [ros-dev] Build with zlib
Hello, from the compilation log you can read:
[CC] lib\3rdparty\zlib\adler32.c [CC] lib\3rdparty\zlib\compress.c [CC] lib\3rdparty\zlib\crc32.c [CC] lib\3rdparty\zlib\gzio.c [CC] lib\3rdparty\zlib\uncompr.c [CC] lib\3rdparty\zlib\deflate.c [CC] lib\3rdparty\zlib\trees.c [CC] lib\3rdparty\zlib\zutil.c [CC] lib\3rdparty\zlib\inflate.c [CC] lib\3rdparty\zlib\infback.c [CC] lib\3rdparty\zlib\inftrees.c [CC] lib\3rdparty\zlib\inffast.c [AR] obj-i386\lib\3rdparty\zlib\zlib.a
why does it compile zlib.a (absolutely unuseful in my opinion) instead of zlib1.dll with its libz.a? This log has been taken from the compilation of ReactOS and *not* from the "make bootcd" session.
Sincerely,
Carlo Bramini.
------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-modeT di Wind http://i-mode.wind.it/
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Sounds like you just aswered the question "Why is it a static library?" with "because it's a static library" and justified it with the fact that it's in the lib folder ;-)
Alex Ionescu schrieb:
Um, because it's a static library? Do you see it in the "dll" directory or in the "lib" directory?
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of carlo.bramix Sent: September-04-07 5:19 AM To: ros-dev Subject: [ros-dev] Build with zlib
Hello, from the compilation log you can read:
[CC] lib\3rdparty\zlib\adler32.c [CC] lib\3rdparty\zlib\compress.c [CC] lib\3rdparty\zlib\crc32.c [CC] lib\3rdparty\zlib\gzio.c [CC] lib\3rdparty\zlib\uncompr.c [CC] lib\3rdparty\zlib\deflate.c [CC] lib\3rdparty\zlib\trees.c [CC] lib\3rdparty\zlib\zutil.c [CC] lib\3rdparty\zlib\inflate.c [CC] lib\3rdparty\zlib\infback.c [CC] lib\3rdparty\zlib\inftrees.c [CC] lib\3rdparty\zlib\inffast.c [AR] obj-i386\lib\3rdparty\zlib\zlib.a
why does it compile zlib.a (absolutely unuseful in my opinion) instead of zlib1.dll with its libz.a? This log has been taken from the compilation of ReactOS and *not* from the "make bootcd" session.
Sincerely,
Carlo Bramini.
Leggi GRATIS le tue mail con il telefonino i-modeT di Wind http://i-mode.wind.it/
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev