[ITK-users] FW: ITK Python wrapping

[Matt McCormick]

Hi Fabio,

Thanks for the updates.

The apparent errors are not actual errors.  These result when CMake
configuration runs (indicated by the preceding "--"), and CMake tests
the availability of compiler features with try_compiles [1].  If an
error occurs, then that feature is not used in the build.

It is good to see that the *.pyd files are there and your Python path.
There should still be *.dll files whose folder needs to be added to
the PATH system environmental variable.  These are usually in the
"bin" instead of "lib" directory. Search for a file
"ITKCommon-4.8.dll" if you built ITK 4.8.

Hope this helps,
Matt

PS. Please reply-to-all so conversations remain on the mailing lists.

[1] http://www.cmake.org/cmake/help/v3.3/command/try_compile.html

On Tue, Aug 25, 2015 at 3:02 AM, D'Isidoro  Fabio <fisidoro at ethz.ch> wrote:
> Sorry forgot the attachments
>
> -----Original Message-----
> From: D'Isidoro Fabio
> Sent: Dienstag, 25. August 2015 09:01
> To: 'Matt McCormick'
> Subject: RE: [ITK-users] ITK Python wrapping
>
> One more thing: in the guide it's written to add to the PATH the directories containing the .dll files, suggesting ITKbuild, ITKbuild/bin and ITKbuild/bin/Release.
>
> However as you can see from the attachments the suggested directory has only executables, while the .lib files (I don't have .dll files) are in the ITKbuild/lib/Release (second attachment)...
>
> Anyway I tried to add the the ITKbuild/lib/Release directory to the PATH but it did not work either.
>
>
> -----Original Message-----
> From: Matt McCormick [mailto:matt.mccormick at kitware.com]
> Sent: Montag, 24. August 2015 17:08
> To: D'Isidoro Fabio
> Cc: insight-users at itk.org
> Subject: Re: [ITK-users] ITK Python wrapping
>
> Hi Fabio,
>
>> - Well, I have a ITKPyBasePython.pyc file in the ITK lib (and the things you told me to check are allright). So the difference is that the name has no underscore _ITKPyBasePython (as reported in the error) and the extension is pyc rather than pyd (although I have read it should not make the difference). Are those things relevant? If yes, how to correct for them? Maybe the dlls were not properly compiled so the underscore is missing?
>
> Both the .pyc and the .pyd files are required.
>
>
>> Depending on your reply to this email, I will then try to build ITK with Python wrapping again so that I can report the compilation failures I got regarding CastXML.
>
> Great, thank you.  A Release build instead of a Debug build is recommended -- build size and runtime performance are greatly improved.  There is on going work to substantially decrease the wrapping build time in ITK Git master, but it is currently unstable.
> The 4.8.0 release is recommended until that is resolved.
>
>
>> About the symbolic link, I just read on the guide "ln -s /path/to/ITK-Wrapped/Wrapping/Generators/Python/WrapITK.pth" and went to find out what ln -s was ... but you are right, the guide says to copy the file, so I guess you don't have improve this part. Maybe just specifiy that there is no need to download Swig.
>
> Thanks for the feedback.  We will improve the wrapping process description.
>
>
>> Thank you, I have spent 5 long days already with no success on this issue (which seems to me a very common issue for users willing to use the Python wrapping, from my extensive google search).
>
> Yes, wrapping has been difficult in the past, but things are changing.
> With your help, it will improve even quicker :-).
>
>
> Thanks,
> Matt