bundle.rst 2.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. CPack Bundle Generator
  2. ----------------------
  3. CPack Bundle generator (macOS) specific options
  4. Variables specific to CPack Bundle generator
  5. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  6. Installers built on macOS using the Bundle generator use the
  7. aforementioned DragNDrop (``CPACK_DMG_xxx``) variables, plus the following
  8. Bundle-specific parameters (``CPACK_BUNDLE_xxx``).
  9. .. variable:: CPACK_BUNDLE_NAME
  10. The name of the generated bundle. This appears in the OSX finder as the
  11. bundle name. Required.
  12. .. variable:: CPACK_BUNDLE_PLIST
  13. Path to an OSX plist file that will be used for the generated bundle. This
  14. assumes that the caller has generated or specified their own Info.plist
  15. file. Required.
  16. .. variable:: CPACK_BUNDLE_ICON
  17. Path to an OSX icon file that will be used as the icon for the generated
  18. bundle. This is the icon that appears in the OSX finder for the bundle, and
  19. in the OSX dock when the bundle is opened. Required.
  20. .. variable:: CPACK_BUNDLE_STARTUP_COMMAND
  21. Path to a startup script. This is a path to an executable or script that
  22. will be run whenever an end-user double-clicks the generated bundle in the
  23. OSX Finder. Optional.
  24. .. variable:: CPACK_BUNDLE_APPLE_CERT_APP
  25. The name of your Apple supplied code signing certificate for the application.
  26. The name usually takes the form ``Developer ID Application: [Name]`` or
  27. ``3rd Party Mac Developer Application: [Name]``. If this variable is not set
  28. the application will not be signed.
  29. .. variable:: CPACK_BUNDLE_APPLE_ENTITLEMENTS
  30. The name of the ``Plist`` file that contains your apple entitlements for sandboxing
  31. your application. This file is required for submission to the Mac App Store.
  32. .. variable:: CPACK_BUNDLE_APPLE_CODESIGN_FILES
  33. A list of additional files that you wish to be signed. You do not need to
  34. list the main application folder, or the main executable. You should
  35. list any frameworks and plugins that are included in your app bundle.
  36. .. variable:: CPACK_BUNDLE_APPLE_CODESIGN_PARAMETER
  37. Additional parameter that will passed to ``codesign``.
  38. Default value: ``--deep -f``
  39. .. variable:: CPACK_COMMAND_CODESIGN
  40. Path to the ``codesign(1)`` command used to sign applications with an
  41. Apple cert. This variable can be used to override the automatically
  42. detected command (or specify its location if the auto-detection fails
  43. to find it).