<div class="gmail_quote">On Mon, Oct 3, 2011 at 10:14 AM, Richard Wackerbarth <span dir="ltr"><<a href="mailto:richard@nfsnet.org">richard@nfsnet.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I don't think that you want the SOURCE file in the bundle.<br>
<br>
First, you need to process the source file with configure_file():<br>
Use ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist as input<br>
and ${CMAKE_CURRENT_BINARY_DIR}/Info.plist as output.<br>
<br>
Then you incorporate the configured version into the bundle:<br>
set_target_properties(${this_target} PROPERTIES MACOSX_BUNDLE_INFO_PLIST ${CMAKE_CURRENT_BINARY_DIR}/Info.plist)<br>
<div class="im"><br>
On Oct 3, 2011, at 8:24 AM, <a href="mailto:g4@novadsp.com">g4@novadsp.com</a> wrote:<br>
<br>
> set_target_properties(${this_target} PROPERTIES MACOSX_BUNDLE_INFO_PLIST ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist)<br>
<br>
</div><div><div></div><div class="h5">--<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<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><br>Either way should be fine. The MACOSX_BUNDLE_INFO_PLIST target property specifies a customization or an override of the CMake provided built-in file "<a href="http://MacOSXBundleInfo.plist.in">MacOSXBundleInfo.plist.in</a>". CMake itself will configure this file into the bundle's Info.plist file. So there's no need for you to call configure_file on it.<br>
<br>But if you do, CMake will do so again anyhow, and you should end up with the same final result.<br><br>I'm looking at the code in "cmLocalGenerator::GenerateAppleInfoPList" to derive this information... (Which is called from Makefile and Xcode generators...)<br>
<br><br>HTH,<br>David<br><br>