Hi,

I’m experimenting with using Cmake’s bundle support on OS-X for a project. (Up 
until now I have assembled the bundle by hand using a separate script which 
also creates the DMG). I have the situation, that I need the executable name to 
be different to the bundle name. MACOSX_BUNDLE_BUNDLE_NAME lets met set the 
name that appears in the CFBundleName key of the Info.plist, but the generated 
bundle still has the name of the target.

I.e I want:

        add_target(foo MACOSX_BUNDLE …. sources )

        set_target_properties(foo PROPERTIES MACOSX_BUNDLE_BUNDLE_NAME 
“Wonderful App”)

And end up with:

        ./Wonderful App.app/Contents/MacOS/foo

Unfortunately it doesn’t work - any suggestions on ways to achieve this? (I’ve 
Googled and the only hits predate the addition of the MACOSX_BUNDLE_ target 
properties)

(Tested with Cmake 2.8.11)

One more thing, is there a standard way to install other components inside the 
bundle? I have seen some examples on the web which hardcode the bundle name as 
the destination path, which feels a bit ugly. (I’m thinking about helper 
applications and dylibs here, as well as the .icns file)

Kind regards,
James

Attachment: smime.p7s
Description: S/MIME cryptographic signature

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to