[CMake] Use of MACOSX_BUNDLE??

[William A. Hoffman]

./CMakeVSNMake71Dev/bin/cmake --help ADD_EXECUTABLE

       ADD_EXECUTABLE(exename [WIN32] [MACOSX_BUNDLE] source1
                      source2 ... sourceN)

   MACOSX_BUNDLE indicates that when build on Mac OSX, executable should
   be in the bundle form.  The MACOSX_BUNDLE also allows several
   variables to be specified:

     MACOSX_BUNDLE_INFO_STRING
     MACOSX_BUNDLE_ICON_FILE
     MACOSX_BUNDLE_GUI_IDENTIFIER
     MACOSX_BUNDLE_LONG_VERSION_STRING
     MACOSX_BUNDLE_BUNDLE_NAME
     MACOSX_BUNDLE_SHORT_VERSION_STRING
     MACOSX_BUNDLE_BUNDLE_VERSION
     MACOSX_BUNDLE_COPYRIGHT

At 06:26 PM 4/11/2006, Lars Pechan wrote:
>Hi all,
>I have the following problem. I generate my wxWidgets project for  
>Xcode on OSX. The result is an app that is not a first-class citizen.  
>For example trying to activate the main window of the generated app  
>is impossible, as is trying to use any of its menus. As a consequence  
>of this I can't debug in Xcode; which is something I'd really like to  
>do.
>
>I know OSX needs a $AppName.app folder with some particular contents  
>in it and found MACOSX_BUNDLE in the manual. Reading the manual I was  
>guessing that all the Info.plist-related stuff, if used, would  
>automatically generate an Info.plist and set up the bundle directory  
>correctly. After having tried this it seems rather clear that that's  
>not the case.
>
>So the question is: How do I use MACOSX_BUNDLE and the associated  
>MACOSX_BUNDLE.... bits to generate a first class , debuggable by  
>Xcode citizen? Or do I have to do all of thi by myself using skeleton  
>files and writing CMake code to set up directories and copy skeleton  
>files across to those?
>
>Thanks for any hints,
>
>/Lars
>_______________________________________________
>CMake mailing list
>CMake at cmake.org
>http://www.cmake.org/mailman/listinfo/cmake