It is actively used in CVS HEAD of ParaView on the Mac to build the standalone paraview client .app bundle.<div><br></div><div>Probably not as easy to understand as you'd like, but it works.<br><br></div><div>This snippet is from the very bottom of ParaView's Applications/Client/CMakeLists.txt file. It's an install rule that runs the configured scripts. (The usage of GetPrerequisites is internal to BundleUtilities which is included in the configured cmake script...)</div>
<div><br></div><div><div># Call this last so the install script runs after the above targets are installed:</div><div>#</div><div>IF(Q_WS_MAC)</div><div> SET(OSX_MAKE_STANDALONE_BUNDLE_CMAKE_SCRIPT "${ParaView_BINARY_DIR}/${PV_EXE_NAME}_OSX_MakeStandAloneBundle.cmake")</div>
<div> SET(OSX_MAKE_STANDALONE_BUNDLE_BASH_SCRIPT "${ParaView_BINARY_DIR}/${PV_EXE_NAME}_OSX_MakeStandAloneBundle.sh")</div><div><br></div><div> CONFIGURE_FILE("${CMAKE_CURRENT_SOURCE_DIR}/<a href="http://CompleteBundle.cmake.in">CompleteBundle.cmake.in</a>"</div>
<div> "${OSX_MAKE_STANDALONE_BUNDLE_CMAKE_SCRIPT}" @ONLY IMMEDIATE)</div><div> CONFIGURE_FILE("${CMAKE_CURRENT_SOURCE_DIR}/<a href="http://CreateBundle.sh.in">CreateBundle.sh.in</a>"</div><div> "${OSX_MAKE_STANDALONE_BUNDLE_BASH_SCRIPT}" @ONLY IMMEDIATE)</div>
<div><br></div><div> INSTALL(SCRIPT "${OSX_MAKE_STANDALONE_BUNDLE_CMAKE_SCRIPT}")</div><div>ENDIF(Q_WS_MAC)</div><div><br></div><div><br></div></div><div>HTH,</div><div>David</div><div><br></div><div><br><div class="gmail_quote">
On Wed, Nov 5, 2008 at 12:19 PM, Stephen Collyer <span dir="ltr"><<a href="mailto:scollyer@netspinner.co.uk">scollyer@netspinner.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">David Cole wrote:<br>
> This line:INSTALL(SCRIPT "${CMAKE_MODULE_PATH}/GetPrerequisites.cmake")<br>
><br>
> doesn't really do anything at "make install" time.<br>
><br>
> GetPrerequisites.cmake just defines a bunch of functions. You have to<br>
> include it and then *call* some of the functions for it to do anything<br>
> useful.<br>
><br>
> So, you should write your own cmake script that gets called at "make<br>
> install" time and then include GetPrerequisites.cmake and call some of the<br>
> functions in it... presumably to install other prerequisite libraries as<br>
> well.<br>
><br>
> Does that make sense?<br>
<br>
</div>Yes, thanks. I must admit I wasn't sure how GetPrerequisites is used,<br>
and I haven't yet had time to look into further. I had cut-n-pasted<br>
that line from something that Bill Hoffman posted once in the<br>
pious hope that it would magically do all the work for me somehow.<br>
<br>
Are there any examples available that show real life usage<br>
of this module ?<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="Wj3C7c">Regards<br>
<br>
Steve Collyer<br>
Netspinner Ltd<br>
_______________________________________________<br>
CMake mailing list<br>
<a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div>