[CMake] Bundle Generator conflicts with MACOSX_BUNDLE
Timothy M. Shead
tshead at k-3d.com
Sat Nov 1 23:29:36 EDT 2008
Mike Arthur wrote:
> On Friday 31 October 2008 16:18:51 Timothy M. Shead wrote:
>> Of course, you still have to provide a mechanism so the executable can
>> be located when your user double-clicks your bundle. That's where
>> CPACK_BUNDLE_STARTUP_COMMAND comes-in ... it copies a bundle-specific
>> file into the Contents/MacOS directory. That file could be a symlink to
>> the actual executable, or a startup script. Note that it is *never*
>> intended to be the executable itself.
> Ah, ok, this wasn't fully understood. Can you suggest how I might make this a
> symlink? Just manually create a relative one and pass it to
That's the (untested) idea - although it occurs to me that the copy
command may try to copy the symlink target instead of the link itself.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 168 bytes
Desc: not available
More information about the CMake