1) Did you mangle the function names? 2) Also, a number of tif files needed changes to avoid warnings on some compilers. If you look at: http://public.kitware.com/cgi-bin/viewcvs.cgi/Utilities/itktiff/?root=Insight you can see files that have a revision other than 1.1 have changes. There is nothing you can do before checking in your changes. This is just a reminder that we'll all need to be vigilant about removing the warnings. 3) What changes do you anticipate in TIFFImageIO? Do all of the itk tests pass?
Bill On Tue, Dec 2, 2008 at 9:17 AM, Mathieu Malaterre <[EMAIL PROTECTED]> wrote: > 'lo > > On Tue, Dec 2, 2008 at 3:06 PM, Rashindra Manniesing > <[EMAIL PROTECTED]> wrote: >> >> >> Finally found some time to update the tiff library - checked out cvs, and >> replaced tiff with latest. Everything now compiles (gcc 4.1.2, linux, 64b). > > pretty darn cool ! > >> Now the functions needs to be updated in itkTIFFImageIO - who is >> maintaining/wrote these image factory? > > Julien Jomier might be... > >> Also, I noticed gdcm was updated to 2.0, which is great! However, 3.10.0 and >> cvs did not have the latest version, or should it still be committed? > > gdcm 2.0 does not compile with compiler such as VS6. However nothing > restrict you from using a system gdcm 2.0 in place of the shipped one. > We are currently working on that for debian people. > > 2cts > -- > Mathieu > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
