On Mon, Oct 3, 2011 at 10:14 AM, Richard Wackerbarth <rich...@nfsnet.org>wrote:
> I don't think that you want the SOURCE file in the bundle. > > First, you need to process the source file with configure_file(): > Use ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist as input > and ${CMAKE_CURRENT_BINARY_DIR}/Info.plist as output. > > Then you incorporate the configured version into the bundle: > set_target_properties(${this_target} PROPERTIES MACOSX_BUNDLE_INFO_PLIST > ${CMAKE_CURRENT_BINARY_DIR}/Info.plist) > > On Oct 3, 2011, at 8:24 AM, g...@novadsp.com wrote: > > > set_target_properties(${this_target} PROPERTIES MACOSX_BUNDLE_INFO_PLIST > ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist) > > -- > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > 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 "MacOSXBundleInfo.plist.in". 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. But if you do, CMake will do so again anyhow, and you should end up with the same final result. I'm looking at the code in "cmLocalGenerator::GenerateAppleInfoPList" to derive this information... (Which is called from Makefile and Xcode generators...) HTH, David
-- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake