[Insight-users] correct numarray version for ITK 2.4.1

[Gaetan Lehmann]

On Mon, 13 Feb 2006 16:21:00 +0100, Zachary Pincus <zpincus at stanford.edu>  
wrote:

> On Feb 13, 2006, at 4:44 AM, Charl P. Botha wrote:
>> However, a darcs checkout from under Windows XP with dar cs 1.0.6pre1
>> (non-cygwin version) via "darcs get
>> http://voxel.jouy.inra.fr/darcs/contrib-itk/WrapITK" gives me the
>> following error:
>>
>> Copying patch 348 of 348... done!
>> Applying patch 320 of 348... Unapplicable patch:
>> Sat Jan 28 19:50:37 W. Europe Standard Time 2006   
>> gaetan.lehmann at jouy.inra.fr
>>   * itkvtk now works
>> darcs.exe: ./ExternalProjects/ItkVtk/Wrapping/Python/itkvtk.py:  
>> openBinaryFile:
>> does not exist (No such file or directory)
>>
>> darcs then terminates, leaving the checkout in a non-updated state.
>> Do you have any ideas on how to fix this?
>
> Patch 320 has a step in which there is a file ItkVtk.py and a file  
> itkvtk.py in the same directory. On case-insensitive filesystems like  
> the one I have on OS X, this fails. I thought windows filesystems were  
> case-sensitive, but clearly there's some related problem.
>
> When WrapITK is declared "beta" or whatever, Gaetan will make a new  
> partial branch in Darcs so that just the current files (and not the  
> hundreds of earlier patches) can be retrieved with Darcs. For now, I  
> suggest just grabbing the nightly tarball:
> http://voxel.jouy.inra.fr/darcs/contrib-itk/WrapITK/WrapITK.tar.gz
>
> If you really need a "live" darcs repository of the code, perhaps (a)  
> Gaetan can branch it soon, or (b) you can revert patch 320 from your  
> linux repository, and then pull from the linux box to the windows box.

I have just added a checkpoint which should solve this issue.
Please, use

   darcs get --partial http://voxel.jouy.inra.fr/darcs/contrib-itk/WrapITK/

and let me now if it works.


BTW, I didn't receive your mail. Is it normal ?
Let me know if I was in the recipients, so I can warn my mail admin if the  
mail was dropped.

>
>> One other question:
>> From reading the documentation, it seems that if you're going to use
>> WrapITK, it's really not necessary to build ITK with its own Python or
>> Tcl wrappings, as long as you have CableSwig built, is that correct?
>
> This is correct. All you need is a standard ITK build tree. You'll need  
> to build with shared libraries, using ITK code from either (a) a CVS  
> checkout from sometime later than 2006-1-31, or (b) ITK 2.4.1 with all  
> the patches in WrapITK/patch/required applied. CableSwig can either be  
> built as part of ITK or built separately.
>
> One last thing:
> In WrapITK, itkPyBuffer should be compatible with Numeric, Numarray, or  
> the new NumPy (the hybrid of the first two, which is to be the single,  
> unified python numeric package). The CMakeLists file will attempt to  
> find out which you have installed.
>
> Let me or Gaetan know if you have any questions.
>
> Zach Pincus
>



-- 
Gaëtan Lehmann
Biologie du Développement et de la Reproduction
INRA de Jouy-en-Josas (France)
tel: +33 1 34 65 29 66    fax: 01 34 65 29 09
http://voxel.jouy.inra.fr