<div dir="ltr"><div><div><div>You'll save many people's frustration by including<span class=""> VTKTargets.cmake in the "make install" target, thank you.<br></span></div><span class="">I found a workaround is to copy</span><span class=""> VTKTargets.cmake from ParaView's build directory to the same place as the installed VTKConfig.cmake, and to replace all occurrences of the build directory by their installation counterparts.<br><br></span></div><span class="">Thank you<br></span></div><span class="">Corinna<br></span><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 29, 2016 at 2:42 PM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">> Would it be easy for you to make the ParaView installation directory usable<br>
> as VTK_DIR by adding the required cmake files? Or is there a more difficult<br>
> problem underneath? The missing VTKTargets.cmake has been discussed several<br>
> times in the past with no real solution.<br>
<br>
</span>We can certainly support that use-case. I've reported an issue:<br>
<a href="https://gitlab.kitware.com/paraview/paraview/issues/16865" rel="noreferrer" target="_blank">https://gitlab.kitware.com/<wbr>paraview/paraview/issues/16865</a><br>
<span class=""><font color="#888888"><br>
Utkarsh<br>
</font></span></blockquote></div><br></div></div></div></div></div></div>