<div class="gmail_quote">On Thu, Apr 15, 2010 at 7:21 AM, Dave Partyka <span dir="ltr"><<a href="mailto:dave.partyka@kitware.com">dave.partyka@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Just thinking out loud, but we could make building HDF5 an "external_project" call instead. This will download/update, configure, build and install hdf5 and then in ParaView we can just FindPackage(HDF5) and give our internal build tree as a hint. We would leave the USE_SYSTEM_HDF5 logic in place and if it is OFF then external_project will be called.<div>
<div></div><div class="h5"><br></div></div></blockquote><div><br>Just a word of caution: you can't simply use ExternalProject_Add and then use FindPackage within the same CMakeLists.txt file for a plain old ParaView build. You'd have to do a "super build" approach where both HDF5 and ParaView are built as ExternalProject_Add calls and then ParaView could use FindPackage to find the (configured/built/installed by previous build steps) HDF5.<br>
<br>You could do ExternalProject_Add to build HDF5 as long as everything that FindPackage currently sets gets set in a predictive fashion (*before* HDF5 itself is downloaded, configured, built or installed...)<br><br><br>
Just thinking out loud, too,<br>David C.<br><br></div></div>