Hello,<div><br></div><div>I have built a ParaView-3.12.0 development release. My goal is to use this development release to compile & link libraries compatible with the Kitware ParaView releases. Ultimately, I hope to contribute my development release for Mac & Linux (x86_64) to the unofficial-dev-install project at <a href="http://code.google.com/p/unofficial-paraview-dev-install/">http://code.google.com/p/unofficial-paraview-dev-install/</a>. However, I am running into a problem. Consider the CMakeLists.txt for my plugin:</div>
<div><div><br></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>FIND_PACKAGE(ParaView REQUIRED)</div></div><div><div>INCLUDE(${PARAVIEW_USE_FILE})</div></div><div><div>ADD_PARAVIEW_PLUGIN(vtkENLILReader "1.0"</div>
</div><div><div> SERVER_MANAGER_XML vtkENLILReader.xml</div></div><div><div> SERVER_MANAGER_SOURCES vtkENLILReader.cxx</div></div><div><div> GUI_RESOURCE_FILES vtkENLILGUI.xml)</div></div><div><div><br></div></div><div>
<div><br></div></div><div><div>Target_LINK_LIBRARIES(vtkENLILReader</div></div><div><div>)</div></div></blockquote><div><br></div><div>When I configure with my ParaView_DIR set to my 3.12.0 development release, the code compiles fine, but the link step has problems with four libraries:</div>
<div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>i686-apple-darwin10-g++-4.2.1: /Users/paraview/paraview/ParaView-3.12.0-Darwin-x86_64/lib/libsiloh5.dylib: No such file or directory</div>
</div><div><div>i686-apple-darwin10-g++-4.2.1: /Users/paraview/paraview/ParaView-3.12.0-Darwin-x86_64/lib/libcgns.a: No such file or directory</div></div><div><div>i686-apple-darwin10-g++-4.2.1: /Users/paraview/paraview/ParaView-3.12.0-Darwin-x86_64/lib/libhdf5.dylib: No such file or directory</div>
</div><div><div>i686-apple-darwin10-g++-4.2.1: /Users/paraview/paraview/ParaView-3.12.0-Darwin-x86_64/lib/libz.dylib: No such file or directory</div></div></blockquote><div><br></div><div>My custom plugin doesn't even use these libraries. I can manually link (excluding the four trouble libraries) and my plugin works with the Kitware release of ParaView-3.12.0. For the record, I see similar behavior when compiling the plugin on Linux with a Linux 3.12.0 development release.</div>
<div><br></div><div>When I look at CMakeFiles/vtkENLILReader.dir/link.txt, all the libraries are set correctly except for these four. I'm not sure what's going on here... These paths seem to be hard-coded in a few places in my development release:</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>lib/paraview-3.12/CMake/ParaViewTargets-debug.cmake</div></div><div><div>lib/paraview-3.12/ParaViewTargets-debug.cmake</div></div><div><div>lib/paraview-3.12/KWCommonLibraryDepends.cmake</div>
</div></blockquote><div>It seems like all libraries _except_ libsiloh5, libcgns, libhdf5 and libz are expanded to ${_IMPORT_PREFIX}/lib/paraview-3.12/ in my link.txt.</div><div><br></div><div>How do I setup my SuperBuild to properly build a development release which can be used to compile & link custom plugins without link problems siloh5, cgns, hdf5 and z?</div>
<div><br></div><div>Thanks,</div><div>Pete</div>