Re: [ros-dev] Build with zlib

[carlo.bramix]

Hello.
No, I didn't see the creation of a DLL from the log file.
Perhaps I had understood that zlib was compiled as a static library (eh eh), but in my opinion this isn't the best way for using a robust, thread safe library like this one.
I also agree that I could explain my idea wrongly.
Searching into the online english dictionary... and I found a better word, perhaps "redundant" sounds better than "unuseful".

Sincerely,

Carlo Bramini.

---------- Initial Header -----------
> From      : [e-mail]

To          : "ReactOS Development List" [e-mail]
Cc          : 
Date      : Wed, 05 Sep 2007 11:21:07 -0400
Subject : Re: [ros-dev] Build with zlib
> Um, because it's a static library? Do you see it in the "dll" directory or
> in the "lib" directory?
>
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] 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
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind
http://i-mode.wind.it/

[Magnus Olsen]

It is allot reason we choice statsic lib.
some program or dll for not use dymatic lib.
and some stuff are being use both in user mode and kmode
for decompress and compress stuff. so zlib need be living in both user mode
and kmode
then is the issue with the host tools they are also need of zlib to build
bootcd.

make it dymsatisc is wasite of time and allot of dublications of same code.
either way staic lib are best way for it can other be use in kmode or user
or at host.

other wise we need dubicate same lib around 10 times or more

----- Original Message ----- 
From: "carlo.bramix" [e-mail]
To: "ros-dev" [e-mail]
Sent: Thursday, September 06, 2007 10:37 AM
Subject: Re: [ros-dev] Build with zlib

Hello.
No, I didn't see the creation of a DLL from the log file.
Perhaps I had understood that zlib was compiled as a static library (eh eh),
but in my opinion this isn't the best way for using a robust, thread safe
library like this one.
I also agree that I could explain my idea wrongly.
Searching into the online english dictionary... and I found a better word,
perhaps "redundant" sounds better than "unuseful".

Sincerely,

Carlo Bramini.

---------- Initial Header -----------
> From      : [e-mail]

To          : "ReactOS Development List" [e-mail]
Cc          :
Date      : Wed, 05 Sep 2007 11:21:07 -0400
Subject : Re: [ros-dev] Build with zlib
> Um, because it's a static library? Do you see it in the "dll" directory or
> in the "lib" directory?
>
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] 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
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-modeT di Wind
http://i-mode.wind.it/

_______________________________________________
Ros-dev mailing list
[e-mail]
http://www.reactos.org/mailman/listinfo/ros-dev