<br><br><div class="gmail_quote">2009/5/14 Gaëtan Lehmann <span dir="ltr"><<a href="mailto:gaetan.lehmann@jouy.inra.fr">gaetan.lehmann@jouy.inra.fr</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Le 12 mai 09 à 20:26, Darren Weber a écrit :<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
2009/5/12 Gaëtan Lehmann <<a href="mailto:gaetan.lehmann@jouy.inra.fr" target="_blank">gaetan.lehmann@jouy.inra.fr</a>><br>
<br>
Le 12 mai 09 à 19:46, Darren Weber a écrit :<br>
<br>
<br>
Hi,<br>
<br>
What's the fix for this issue with dynamic lib builds with python wrapping in ITK (3.12)? The linker appears to be building a dynamic lib (or shared lib, *.so), but perhaps the linker option "-dynamiclib" is missing somewhere in the cmake config? Please tell me if there is simple patch to fix this. Could it be an issue with using "-Wno-long-double" for the vnl numerics wrapping?<br>
<br>
This build uses CableSwig build options (ie, cmake ... -D ITK_CSWIG_PYTHON:BOOL=ON ...), rather than USE_WRAP_ITK. What is the most preferred wrapping method for ITK @3.12? I noticed mention of a new release, 3.14, in the wings and nearly available. Does the new release (3.14) resolve build problems for wrappers (or is the focus of that release elsewhere)?<br>
<br>
<br>
Hi,<br>
<br>
I can't recall any problem while building WrapITK on Mac OS X.<br>
Have you tried with WrapITK?<br>
<br>
Regards,<br>
<br>
Gaëtan<br>
<br>
<br>
I posted a build error the other day when USE_WRAP_ITK was ON. The title of that post was "ITK wrap build error on itkLaplacianRecursiveGaussianImageFilterPython.o" The error message was obtuse. I've had no feedback on that post.<br>
<br>
</blockquote>
<br></div>
ok, I've missed that one. The message is not much informative for me as well.<br>
It seems that you are using stuff from macport. Can you try to build cable swig and itk with the compiler provided with xcode and the default compiler options? That's what I'm doing here without trouble.<br>
<br>
You can disable most of the WRAP_* options in cmake for the tests, and keep only one dimension in WRAP_ITK_DIMS, to make things a bit faster.<div class="im"></div></blockquote><div><br><br>As a MacPorts developer, working on a Portfile for ITK called InsightToolkit, I need to and want to work with MacPorts. I'm currently updating this port to ITK @<a href="http://3.12.0.">3.12.0.</a> MacPorts provides a way to document and automate build configurations, including dependencies. It helps me, while simultaneously making my work available to anyone using MacPorts. AFAIK, the MacPorts compiler is provided by an xcode installation (I can double check the defaults or change to a specific compiler at will). Most of the ITK build is fine (as expected), but I've run into troubles with wrapping ITK. It looks like it's best to stick with python wrapping (leave out java and tcl, or whatever else, for now). As a python programmer myself, that preference is understandable, although I thought tcl would be fine too, but maybe not. I have too much to learn about wrapping - ignorance is bliss, until you need something to work when it doesn't work.<br>
<br>BTW, there is a VTK 5.4.0 port in vtk-devel in macports. In that port, just about everything is worked out, including wrapping, MPI, Boost, databases, etc. I'm also working on a cableswig port, which builds and installs fine, but there's an issue with finding the SWIG Lib directory for cswig.<br>
<br>So, this port development is working with the wrapITK in the ITK 3.12.0 release. It also pulls in the CableSwig-ITK-3.12.0 release and puts it into <ITK-srcPath>/Utilities/CableSwig and assumes that this cableswig is built by default (i.e., no cmake variables are explicitly set to switch on the build for it). The cmake vars for the wrapITK are specified:<br>
<br> -DUSE_WRAP_ITK:BOOL=ON \<br> -DITK_USE_REVIEW:BOOL=ON \<br> -DGUILE_EXECUTABLE:FILEPATH=${prefix}/bin/guile \<br> -DGUILE_LIBRARY:FILEPATH=${prefix}/lib/libguile.dylib \<br> -DGUILE_INCLUDE_PATH:PATH=${prefix}/include/guile \<br>
-DSWIG_BUILD_EXAMPLES:BOOL=ON<br><br>The following are set by default (maybe a cmake module does this?):<br><br> #WRAP_BinaryMorphology ON<br> #WRAP_Calculators ON<br> #WRAP_Compose ON<br>
#WRAP_DeformableTransforms ON<br> #WRAP_Denoising ON<br> #WRAP_DistanceMap ON<br> #WRAP_EdgesAndContours ON<br> #WRAP_FFT ON<br> #WRAP_FFTW OFF<br>
#WRAP_Filtering ON<br> #WRAP_IO ON<br> #WRAP_ITK_DIMS 2;3<br> #WRAP_ITK_INSTALL_PREFIX /lib/InsightToolkit/WrapITK<br> #WRAP_ITK_JAVA ON<br>
#WRAP_ITK_PYTHON ON<br> #WRAP_ITK_TCL ON<br> #WRAP_IntensityFilters ON<br> #WRAP_Interpolators ON<br> #WRAP_Iterators OFF<br> #WRAP_LevelSet ON<br>
#WRAP_Morphology ON<br> #WRAP_PixelMath ON<br> #WRAP_Registration ON<br> #WRAP_Resize ON<br> #WRAP_Review ON<br> #WRAP_SegmentationAndThreshold ON<br>
#WRAP_SegmentationValidation ON<br> #WRAP_SimpleFilters ON<br> #WRAP_UnaryPixelMath ON<br> #WRAP_complex_double OFF<br> #WRAP_complex_float ON<br> #WRAP_covariant_vector_double OFF<br>
#WRAP_covariant_vector_float ON<br> #WRAP_double OFF<br> #WRAP_float ON<br> #WRAP_rgb_unsigned_char OFF<br> #WRAP_rgb_unsigned_short ON<br> #WRAP_rgba_unsigned_char OFF<br>
#WRAP_rgba_unsigned_short ON<br> #WRAP_signed_char OFF<br> #WRAP_signed_long OFF<br> #WRAP_signed_short OFF<br> #WRAP_unsigned_char OFF<br> #WRAP_unsigned_long OFF<br>
#WRAP_unsigned_short ON<br> #WRAP_vector_double OFF<br> #WRAP_vector_float ON<br><br><br><br>Thanks for helping out, I will look at your CmakeCache.txt today.<br><br></div></div>
Take care,<br>Darren<br><br>