... | ... | @@ -174,6 +174,8 @@ scripts?". <http://s.sudre.free.fr/Stuff/PackageMaker_Howto.html> . In |
|
|
summary the arguments correspond to $0 Script path, $1 Package path, $2
|
|
|
Target location, and $3 Target Volume.
|
|
|
|
|
|
_NOTE: in recent OS X versions, PackageMaker has been deprecated and was recently removed. As a result, this generator will not work with recent OS X versions. The [ProductBuild](https://cmake.org/cmake/help/v3.7/module/CPackProductBuild.html) generator replaces it, and should offer similar functionality._
|
|
|
|
|
|
## OSXX11 (OSX only)
|
|
|
|
|
|
Mac OSX X11 Bundle. Requires hdiutil for creating the package.
|
... | ... | @@ -321,14 +323,14 @@ The prototype bundle generator uses the following variables: |
|
|
- CPACK_PACKAGE_FILE_NAME - provides the name of the final
|
|
|
compressed disk image (the name of the file that is distributed).
|
|
|
- CPACK_PACKAGE_ICON - provides the icon for the mounted disk image
|
|
|
(appears after the user mounts the disk image).
|
|
|
(appears after the user mounts the disk image). NOTE: Icon must be [an approved OS X application icon resolution](http://iconhandbook.co.uk/reference/chart/osx/). Attempting to specify an icon that is not one of these sizes will result in the package having no icon.
|
|
|
- CPACK_BUNDLE_NAME - provides the bundle name (displayed in the
|
|
|
finder underneath the bundle icon).
|
|
|
- CPACK_BUNDLE_ICON - provides the bundle icon (displayed in the
|
|
|
/Applications folder, on the dock, etc).
|
|
|
- CPACK_BUNDLE_PLIST - path to a file that will become the bundle
|
|
|
plist.
|
|
|
- CPACK_BUNDLE_STARTUP_COMMAND - path to a file that will be
|
|
|
plist. AN example of generating a Plist automatically from CMake variables can be found [here](https://github.com/Amber-MD/cmake-buildscripts/blob/9571b0236a86f11c52463853614ae7809dc4d0ac/Packaging.cmake#L100) and [here](https://github.com/Amber-MD/cmake-buildscripts/blob/master/packaging/Info.in.plist).
|
|
|
- CPACK_BUNDLE_STARTUP_COMMAND - path to a file (in your current build directory) that should be
|
|
|
executed when the user opens the bundle. Could be a shell-script or
|
|
|
a binary.
|
|
|
|
... | ... | |