[Insight-users] unable to build itk without building zlib and png libs

[Luis Ibanez]

Hi Gaetan,

These libraries (PNG, ZLIB...) account for a small size both in
source code and binary code. The extra memory required for having
multiple copies in your system is negligeable compared to the amount
of space that ITK and your applications will take.

If you feel motivated to attempt reverting the mangling in your
system, you are certainly welcome to do so. You probably will
rencounter the problem that we described as soon as you start
combining multiple toolkits in your final application.

The names of the libraries (PNG, ZLIB...) have been changed in ITK
and VTK, to prevent any potential confusion at link time. They are
now: itkzlib, itkpng... etc.


It is probably not a good use of your time to attempt to revert the
mangling. Just do a "du" on the ITK source tree and  evaluate how
much time you will have to spend for so little memory (the memory
of the PNG and ZLIB libraries).



Regards,


    Luis


----------------------
Gaetan Lehmann wrote:

> 
> Hi Luis,
> 
> On Wed, 05 Jan 2005 15:35:47 -0500, Luis Ibanez 
> <luis.ibanez at kitware.com>  wrote:
> 
>> The reason is that it became very hard to manage the cases where other
>> toolkits such as VTK and FLTK also linked to PNG and ZLIB libraries,
>> since you will have to ensure that they are all of the same version.
> 
> 
> On another hand, it's quite strange to have the same lib in different  
> files on the same system, and I think linux distros make possible to  
> ensure that libs are all of the same version.
> I'm currently building rpm packages for mandrake linux, and I think it  
> would be really cleaner to use system libs.
> 
> I'm really far of a compiler specialist, but if it is possible, it 
> would  be really nice to keep those options :-)
> 
> Regards,
>