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. 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. 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.
Thank you Corinna On Sat, Aug 27, 2016 at 12:27 PM, Utkarsh Ayachit < [email protected]> wrote: > > For this purpose I configure ParaView with the > > -DUSE_EXTERNAL_VTK=ON option, but I get a bunch of errors. > > Before I attach lengthy error logs, I'd like to ask whether this can > work at > > all? > > No, it's not supported and there are no indications that it will any > time soon unless someone from the community takes it up. > > > The background of my request is that I need to develop a ParaView plugin > > which links a software tool that depends on VTK by itself. I couldn't > find a > > possibility to link this tool against the VTK which is included in > ParaView. > > You should be able to set your VTK_DIR to ParaViewBuildDir/VTK. >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
