CMake/Modules/CPackBundle.cmake

71 lines
2.6 KiB
CMake
Raw Normal View History

Simplify CMake per-source license notices Per-source copyright/license notice headers that spell out copyright holder names and years are hard to maintain and often out-of-date or plain wrong. Precise contributor information is already maintained automatically by the version control tool. Ultimately it is the receiver of a file who is responsible for determining its licensing status, and per-source notices are merely a convenience. Therefore it is simpler and more accurate for each source to have a generic notice of the license name and references to more detailed information on copyright holders and full license terms. Our `Copyright.txt` file now contains a list of Contributors whose names appeared source-level copyright notices. It also references version control history for more precise information. Therefore we no longer need to spell out the list of Contributors in each source file notice. Replace CMake per-source copyright/license notice headers with a short description of the license and links to `Copyright.txt` and online information available from "https://cmake.org/licensing". The online URL also handles cases of modules being copied out of our source into other projects, so we can drop our notices about replacing links with full license text. Run the `Utilities/Scripts/filter-notices.bash` script to perform the majority of the replacements mechanically. Manually fix up shebang lines and trailing newlines in a few files. Manually update the notices in a few files that the script does not handle.
2016-09-27 22:01:08 +03:00
# Distributed under the OSI-approved BSD 3-Clause License. See accompanying
# file Copyright.txt or https://cmake.org/licensing for details.
#.rst:
# CPackBundle
# -----------
#
# CPack Bundle generator (Mac OS X) specific options
#
# Variables specific to CPack Bundle generator
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#
# Installers built on Mac OS X using the Bundle generator use the
# aforementioned DragNDrop (CPACK_DMG_xxx) variables, plus the following
# Bundle-specific parameters (CPACK_BUNDLE_xxx).
#
# .. variable:: CPACK_BUNDLE_NAME
#
# The name of the generated bundle. This appears in the OSX finder as the
# bundle name. Required.
#
# .. variable:: CPACK_BUNDLE_PLIST
#
# Path to an OSX plist file that will be used for the generated bundle. This
# assumes that the caller has generated or specified their own Info.plist
# file. Required.
#
# .. variable:: CPACK_BUNDLE_ICON
#
# Path to an OSX icon file that will be used as the icon for the generated
# bundle. This is the icon that appears in the OSX finder for the bundle, and
# in the OSX dock when the bundle is opened. Required.
#
# .. variable:: CPACK_BUNDLE_STARTUP_COMMAND
#
# Path to a startup script. This is a path to an executable or script that
# will be run whenever an end-user double-clicks the generated bundle in the
# OSX Finder. Optional.
#
# .. variable:: CPACK_BUNDLE_APPLE_CERT_APP
#
# The name of your Apple supplied code signing certificate for the application.
# The name usually takes the form "Developer ID Application: [Name]" or
# "3rd Party Mac Developer Application: [Name]". If this variable is not set
# the application will not be signed.
#
# .. variable:: CPACK_BUNDLE_APPLE_ENTITLEMENTS
#
# The name of the plist file that contains your apple entitlements for sandboxing
# your application. This file is required for submission to the Mac App Store.
#
# .. variable:: CPACK_BUNDLE_APPLE_CODESIGN_FILES
#
# A list of additional files that you wish to be signed. You do not need to
# list the main application folder, or the main executable. You should
# list any frameworks and plugins that are included in your app bundle.
#
# .. variable:: CPACK_BUNDLE_APPLE_CODESIGN_PARAMETER
#
# Additional parameter that will passed to codesign.
# Default value: "--deep -f"
#
# .. variable:: CPACK_COMMAND_CODESIGN
#
# Path to the codesign(1) command used to sign applications with an
# Apple cert. This variable can be used to override the automatically
# detected command (or specify its location if the auto-detection fails
# to find it.)
#Bundle Generator specific code should be put here