[Insight-developers] Itkzlib stuck at version 1.1.4?

[Luis Ibanez]

Hi Sean,

Yes, ITK and VTK "share" many of these libraries.

However, they are not linked in any way through CVS.

The process of updating the libraries will have to
be done independently on each toolkit (ITK/VTK).

I would suggest to start with and easy chunk and just
update the zlib library in ITK. If that goes well,
then make the same updates in VTK.

Then move to jpeg... and so on.

Each one of those updates will take approximately one
week. Committing the changes themselves will be just a
matter of hours, but stabilizing the Dashboard in all
the platforms after the commits does typically requires
a week of discontinuous work.

You want to run Experimental builds in at least Windows,
Linux and Mac, before committing the changes to the CVS
repository.

It is also strongly recommended to commit changes early
in the morning, so you will see the results of the
continuous builds during the day, and will have a chance
to fix them before the modifications affect the entire
Nightly build of the next day.


   Please let us know if you encounter any major problems,


     Thanks


        Luis



-----------------
Sean McBride wrote:
> On 7/19/07 11:36 AM, Luis Ibanez said:
> 
> 
>>Both sounds like a firm vote for updating the zlib library in ITK.
>>
>>   Any volunteers ?
> 
> 
> Luis,
> 
> Maybe I can volunteer after all.  I took a look at 1.1.4 and VTK's CVS,
> and it seems there are almost no local changes.  And the file structure
> of 1.2.3 looks basically the same.  I think it would be straightforward
> to update.
> 
> However, I also notice that zlib is part of ITK, VTK, CMake, and maybe
> other projects like ParaView that I don't use.  I assume we'd want to
> change them all, to stay in sync.  How does that work?  It seems each
> project has a separate CVS repository.
> 
> Cheers,
>