[ITK-users] [Paraview] compile itk (VTKGlue ON) with vtk from paraview

[Dr. Roman Grothausmann]

Hi Matt,

On 26/01/15 17:54, Matt McCormick wrote:
 > I do not think the Midas Journal will be able to build your plugin.

OK, so I added a VTK test program. Is there a way to test if the automatic 
testing environment would be able to build and run my VTK test program BEFORE 
submitting the contribution to Midas?
(My last submission never got tested by the system so far, i.e. there is no 
colde review reported:
http://www.vtkjournal.org/browse/publication/949)

 > I would recommend creating build instructions to build against a
 > ParaView build tree.  I have just verified that ITK builds with the
 > ITKVtkGlue module ON when pointing VTK_DIR to the <ParaView-build>/VTK
 > directory.

Did You use BUILD_SHARED_LIBS ON for both ITK and ParaView? ITK also compiles 
fine without any errors for me if I use BUILD_SHARED_LIBS OFF, however the 
problems then arise when compiling the plugin.
If You like, You can test the compilation of the plugin with the code from the 
git repository:
https://github.com/romangrothausmann/FacetAnalyser

Many thanks for looking into this.
Roman


On 26/01/15 17:54, Matt McCormick wrote:
> Hi Roman,
>
> Thanks for the update. Great to hear about the Midas Journal article!
>
> I do not think the Midas Journal will be able to build your plugin.
>
> I would recommend creating build instructions to build against a
> ParaView build tree.  I have just verified that ITK builds with the
> ITKVtkGlue module ON when pointing VTK_DIR to the <ParaView-build>/VTK
> directory.
>
> I don't see the install tree VTKTargets.cmake file in my ParaView
> build, either. In the long term, the ParaView CMake configuration
> should be corrected.
>
> HTH,
> Matt
>
> On Mon, Jan 26, 2015 at 4:02 AM, Dr. Roman Grothausmann
> <grothausmann.roman at mh-hannover.de> wrote:
>> Hi Matt,
>>
>>
>> Thank You very much for Your reply.
>> I can only find one VTKTargets.cmake in
>> /opt/compilation/paraview-git_build/VTK/
>> It seems though that it is lacking the relevant entries for the libraries
>> that troubled me, e.g. vtkPVPythonCatalyst and
>> vtkUtilitiesPythonInitializer.
>>
>> I'm about to publish the ITK-VTK PV plugin in the Midas Journal, what
>> installation instructions should I give there?
>> Will the testing environment be able to compile this plugin and its tests or
>> should I disable automatic testing for this contribution?
>>
>> Many thanks for looking into this.
>> Roman
>>
>>
>> On 23/01/15 18:15, Matt McCormick wrote:
>>>
>>> Hi Roman,
>>>
>>> Thanks for looking into the issue and reporting it to the mailing list.
>>>
>>> Paraview should be installing VTKTargets.cmake, which tells the build
>>> system where to find the libraries.  Note that there might be two
>>> VTKTargets.cmake files that are generated -- one for the build tree
>>> and one for the install tree.
>>>
>>> HTH,
>>> Matt
>>>
>>> On Fri, Jan 23, 2015 at 4:20 AM, Dr. Roman Grothausmann
>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>
>>>>
>>>> On 22/01/15 11:21, Dr. Roman Grothausmann wrote:
>>>>>
>>>>>
>>>>> Adding the abs. file locations to the build command does not help nor
>>>>> does
>>>>> -L/opt/paraview-4.3.1_git/lib/paraview-4.3/
>>>>
>>>>
>>>>
>>>> I figured that the vtk dynamic libraries of PV have the ending *-pv4.3.so
>>>> which seems to be the reason why the linker does not find them. If I
>>>> create
>>>> symbolic links to these files without the extension:
>>>>
>>>> cd /opt/compilation/paraview-git_build/lib/
>>>> for i in *-pv*.so; do ln -s $i ${i%-pv*}.so; done
>>>>
>>>> and adding -L/opt/compilation/paraview-git_build/lib/ to CMAKE_CXX_FLAGS
>>>> the compilation of ITK succeeds.
>>>>
>>>> I wonder, is that the way it's meant to be done?
>>>>
>>>>
>>>>
>>>>> What am I missing in my configuration of PV and ITK?
>>>>>
>>>>> When and where should I specify:
>>>>> CMAKE_CXX_FLAGS                  -fPIC
>>>>> BUILD_SHARED_LIBS                ON/OFF
>>>>>
>>>>> Is this the right VTK_DIR specification for ITK:
>>>>> /opt/compilation/ParaView-v4.3.1/build/VTK
>>>>> or
>>>>> /opt/paraview-4.3.1_git/lib/cmake/paraview-4.3
>>>>>
>>>>>
>>>>>
>>>>> Many thanks for any help or hints.
>>>>> Roman
>>>>>
>>>>>
>>>>
>>>> --
>>>> Dr. Roman Grothausmann
>>>>
>>>> Tomographie und Digitale Bildverarbeitung
>>>> Tomography and Digital Image Analysis
>>>>
>>>> Institut für Funktionelle und Angewandte Anatomie, OE 4120
>>>> Medizinische Hochschule Hannover
>>>> Carl-Neuberg-Str. 1
>>>> D-30625 Hannover
>>>>
>>>> Tel. +49 511 532-9574
>>>> _____________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Kitware offers ITK Training Courses, for more information visit:
>>>> http://www.kitware.com/products/protraining.php
>>>>
>>>> Please keep messages on-topic and check the ITK FAQ at:
>>>> http://www.itk.org/Wiki/ITK_FAQ
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/insight-users
>>
>>
>> --
>> Dr. Roman Grothausmann
>>
>> Tomographie und Digitale Bildverarbeitung
>> Tomography and Digital Image Analysis
>>
>> Institut für Funktionelle und Angewandte Anatomie, OE 4120
>> Medizinische Hochschule Hannover
>> Carl-Neuberg-Str. 1
>> D-30625 Hannover
>>
>> Tel. +49 511 532-9574

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut für Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-9574