<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"corinna reuter" <corinnareuter75@gmail.com><br><b>To: </b>"Utkarsh Ayachit" <utkarsh.ayachit@kitware.com><br><b>Cc: </b>"ParaView" <paraview@paraview.org><br><b>Sent: </b>Sunday, August 28, 2016 3:28:51 PM<br><b>Subject: </b>Re: [Paraview] Is USE_EXTERNAL_VTK supported with ParaView 5.1.2?<br><div><br></div><div dir="ltr"><div><div><div><div>Thank you, I will try if that works. Now that you mention it, I think I remember that I have been successful in a similar situation quite some time ago by using the build directory.<br></div>However, the problem with this is that I would have to always copy around the complete build directory between production servers. At the moment I only install the installation directory on those servers. (The much smaller installation directory helps to reduce the startup time significantly.) In the installation directory, "VTKTargets.cmake" is missing, so that other projects cannot use this as VTK_DIR.<br></div>Would it be easy for you to make the ParaView installation directory usable as VTK_DIR by adding the required cmake files? Or is there a more difficult problem underneath? The missing VTKTargets.cmake has been discussed several times in the past with no real solution.<br></div></div></div></blockquote><div><br></div><div>Hi, just to let you know that I add try something very similar that is building my app (using Feelpp library) using Paraview/VTK instead of plain VTK.</div><div>To do so we made something like this:</div><div><br></div><div><p style="margin: 0px;" data-mce-style="margin: 0px;">if ( FEELPP_ENABLE_VTK )<br># First try to find ParaView<br>FIND_PACKAGE(ParaView NO_MODULE<br> PATHS $ENV{PARAVIEW_DIR} ${MACHINE_PARAVIEW_DIR} )</p><p style="margin: 0px;" data-mce-style="margin: 0px;">if(ParaView_FOUND)<br> message(STATUS "[ParaView] Use file: ${PARAVIEW_USE_FILE}")<br> INCLUDE(${PARAVIEW_USE_FILE})</p><p style="margin: 0px;" data-mce-style="margin: 0px;"># trying to load a minimal vtk<br> IF (TARGET vtkParallelMPI)<br> FIND_PACKAGE(ParaView QUIET COMPONENTS vtkParallelMPI NO_MODULE<br> PATHS $ENV{PARAVIEW_DIR} ${MACHINE_PARAVIEW_DIR} )<br> message(STATUS "[ParaView] Loading vtkParallelMPI module")<br> ENDIF ()<br> IF (TARGET vtkPVCatalyst)<br> FIND_PACKAGE(ParaView COMPONENTS vtkPVCatalyst NO_MODULE<br> PATHS $ENV{PARAVIEW_DIR} ${MACHINE_PARAVIEW_DIR} )<br> message(STATUS "[ParaView] Loading vtkPVCatalyst module")<br> ENDIF ()<br> IF (TARGET vtkPVPythonCatalyst)<br> FIND_PACKAGE(ParaView COMPONENTS vtkPVPythonCatalyst NO_MODULE<br> PATHS $ENV{PARAVIEW_DIR} ${MACHINE_PARAVIEW_DIR} )<br> message(STATUS "[ParaView] Loading vtkPVPythonCatalyst module")<br> ENDIF ()</p><p style="margin: 0px;" data-mce-style="margin: 0px;"># Enable VTK exporter and insitu in config<br> IF (TARGET vtkPVCatalyst AND TARGET vtkPVPythonCatalyst)<br> set(FEELPP_VTK_INSITU_ENABLED 1)<br> message(STATUS "In-situ visualisation enabled (vtkPVCatalyst, vtkPVPythonCatalyst).")<br> ENDIF()<br> <br> # Mark VTK and ParaView as available<br> set(FEELPP_HAS_VTK 1)<br> set(FEELPP_HAS_PARAVIEW 1)<br> # Check for version to ensure that we are able to<br> # use an external communicator<br> set(VTK_HAS_PARALLEL 0)<br> if( VTK_MAJOR_VERSION EQUAL 6 OR VTK_MAJOR_VERSION GREATER 6 )<br> set(VTK_HAS_PARALLEL 1)<br>endif()</p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br> INCLUDE_DIRECTORIES(${VTK_INCLUDE_DIRS})<br> INCLUDE_DIRECTORIES(${ParaView_INCLUDE_DIRS})<br> INCLUDE_DIRECTORIES(${VTK_INCLUDE_DIRS})<br> SET(FEELPP_LIBRARIES ${ParaView_LIBRARIES} ${FEELPP_LIBRARIES})<br> SET(FEELPP_LIBRARIES ${VTK_LIBRARIES} ${FEELPP_LIBRARIES})<br> SET(FEELPP_ENABLED_OPTIONS "${FEELPP_ENABLED_OPTIONS} ParaView/VTK" )</p><p style="margin: 0px;" data-mce-style="margin: 0px;">message(STATUS "Found ParaView ${PARAVIEW_VERSION_FULL}/VTK ${VTK_MAJOR_VERSION}.${VTK_MINOR_VERSION}")<br> endif()</p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;"># If ParaView was not found we try to find VTK<br> if(NOT ParaView_FOUND)<br> message(STATUS "ParaView could not be found or is not compatible with Feel++. Looking for VTK...")<br> FIND_PACKAGE(VTK QUIET)<br>if( VTK_FOUND )</p><p style="margin: 0px;" data-mce-style="margin: 0px;">....</p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;">It compiles without any problem.</p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;">On Debian/Testing this won't work with packaged paraview. The package need to be reworked in order to use it for providing vtk.</p><p style="margin: 0px;" data-mce-style="margin: 0px;">It consists mainly in adding some "missing files" into the paraview-dev package.</p><p style="margin: 0px;" data-mce-style="margin: 0px;">I'm trying to fix this </p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;">However I run into a problem regarding paraview and vtk python bindings.</p><p style="margin: 0px;" data-mce-style="margin: 0px;">In a "standard" installation of paraview we end-up with the following directories:</p><p style="margin: 0px;" data-mce-style="margin: 0px;">../site-packages/paraview/vtk </p><p style="margin: 0px;" data-mce-style="margin: 0px;">../site-packages/vtk</p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;">These 2 directories contains the same python files except for the __init__.py files.</p><p style="margin: 0px;" data-mce-style="margin: 0px;">The last directory (vtk) also contains some shared libs.</p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;">Would it be possible to somehow to have only on vtk directory into site-packages?</p><p style="margin: 0px;" data-mce-style="margin: 0px;">This would avoid a clash between python-paraview package and python-vtk6 package..</p><p style="margin: 0px;" data-mce-style="margin: 0px;">or to use python-vtk6 package to provide ../site-packages/vtk as it's done right now</p><p style="margin: 0px;" data-mce-style="margin: 0px;">(Besides paraview 5.1.2 actually provides vtk7 which is not packaged so far...)</p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;">Any idea or comments to work around this problem</p><p style="margin: 0px;" data-mce-style="margin: 0px;">Best.</p><div><br></div></div><div></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div dir="ltr"><div>Thank you<br></div>Corinna<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 27, 2016 at 12:27 PM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank" data-mce-href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" data-mce-style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;"><span class="">> For this purpose I configure ParaView with the<br> > -DUSE_EXTERNAL_VTK=ON option, but I get a bunch of errors.<br> > Before I attach lengthy error logs, I'd like to ask whether this can work at<br> > all?<br> <br> </span>No, it's not supported and there are no indications that it will any<br> time soon unless someone from the community takes it up.<br><span class=""><br> > The background of my request is that I need to develop a ParaView plugin<br> > which links a software tool that depends on VTK by itself. I couldn't find a<br> > possibility to link this tool against the VTK which is included in ParaView.<br> <br> </span>You should be able to set your VTK_DIR to ParaViewBuildDir/VTK.<br></blockquote></div><br></div><br>_______________________________________________<br>Powered by www.kitware.com<br><div><br></div>Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html<br><div><br></div>Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView<br><div><br></div>Search the list archives at: http://markmail.org/search/?q=ParaView<br><div><br></div>Follow this link to subscribe/unsubscribe:<br>http://public.kitware.com/mailman/listinfo/paraview<br></blockquote><div><br></div></div></body></html>