summaryrefslogtreecommitdiffstats
path: root/Modules/CPack.cmake
Commit message (Collapse)AuthorAgeFilesLines
* Help: Fix CPack module docs on config file for source packageJoachim Wuttke (h)2020-07-081-1/+1
|
* Help: module CPack: improve summary and IntroductionJoachim Wuttke (o)2020-02-141-12/+12
| | | | | | | | | | | | * In summary: * we configure generators, not the generated installers * we generate installers or source packages, not source package installers * In Introduction: * Make paragraph on binary installers more concise * Remove example that refered to CMake source tree * Add paragraph on source packages * omit the parenthesis on graphical installers
* Help: module CPack: Make internal hyperlink target more uniqueBrad King2020-02-121-3/+3
| | | | We already have a `.. _targets:` in `Help/command/install.rst`.
* Help: module CPack: New section on targets.Joachim Wuttke (o)2020-02-121-7/+21
| | | | | To explain in full detail to what extent the targets package and package_source are supported by different generators.
* Help: module CPack: add cross-reference to cpack-generators(7).Joachim Wuttke (o)2020-02-121-0/+2
|
* Help: module CPack. Explain usage of the build targets.Joachim Wuttke (o)2020-02-121-7/+11
| | | | | Explain the usage of the two new build targets, package and package_source.
* Help: module CPack: correction: 2 config files are generated, not just 1Joachim Wuttke (o)2020-02-121-3/+4
| | | | Besides CPackConfig.cmake, the module also generates CPackSourceConfig.cmake.
* Help: CPack module: Correct the summary (configure, not build)Joachim Wuttke (o)2020-02-121-1/+1
| | | | | Including CPack does not "build" installers. It just *configures* them.
* CPack: Deprecate OSXX11 generatorBrad King2020-01-311-1/+1
| | | | | | | | | | The CPack OSXX11 generator has not had any updates since 2011 except as part of sweeping maintenance changes. It also creates packages with a OSXScriptLauncher binary that has only ppc and i386 architectures which are not supported by Apple anymore. Furthermore, the generator is not even mentioned in our documentation. Add a deprecation warning. Fixes: #20235
* CPack: Deprecate PackageMaker generatorBrad King2020-01-311-1/+1
| | | | | | | Xcode no longer distributes the PackageMaker tools. Add a deprecation warning when the generator is used. Issue: #20235
* Merge topic 'cpack-deb-fix-description'Brad King2020-01-271-1/+2
|\ | | | | | | | | | | | | baec299ecd CPack: Fix regression in Deb description Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4271
| * CPack: Fix regression in Deb descriptionKyle Edwards2020-01-241-1/+2
| | | | | | | | Fixes: #20254
* | CPack: mark options as advanced only if definedBen Boeckel2020-01-141-32/+39
| |
* | Merge topic 'fix-cpack-deb-description-file'Brad King2020-01-131-1/+3
|\ \ | |/ | | | | | | | | | | d491f34a5e CPack: Fix regression in DEB generator description Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4204
| * CPack: Fix regression in DEB generator descriptionKyle Edwards2020-01-101-1/+3
| | | | | | | | Fixes: #20102
* | Merge topic 'remove-CPACK_INSTALL_CMAKE_CONFIGURATIONS'Craig Scott2019-11-121-7/+0
|\ \ | |/ | | | | | | | | | | | | 1d1fa5d3e4 Tests: Add RunCMake.CPackCommandLine case for multi-config package 108207cc84 CPack: Remove CPACK_INSTALL_CMAKE_CONFIGURATIONS Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4025
| * CPack: Remove CPACK_INSTALL_CMAKE_CONFIGURATIONSAlex Turbov2019-11-111-7/+0
| | | | | | | | | | | | | | | | | | | | | | In commit da5ac4bb60 (cpack: Add `CPACK_INSTALL_CMAKE_CONFIGURATIONS` variable, 2019-07-10, v3.16.0-rc1~165^2) we added both the variable and support for `cpack -C` with multiple configurations. Drop the variable because the `package` target cannot ensure that all of the configurations are built. Keep the command-line interface so that it can be used manually in scripts. Fixes: #19918
* | CPack/NSIS: Add option for custom Uninstall filenameJohnny Jazeix2019-10-251-0/+2
|/ | | | Fixes: #10728
* cpack: Add `CPACK_INSTALL_CMAKE_CONFIGURATIONS` variableAlex Turbov2019-08-301-0/+7
| | | | | | | | | For the multi-configuration generators one can specify the list of configurations to include in the package. E.g. having a project, where debug libraries have a suffix to distinct them from the release builds, one can build the package containing both `Debug` and `Release` binaries.
* CPack: Introduce CPACK_INSTALL_SCRIPTS variableAlex Turbov2019-07-211-1/+15
| | | | | | | | | | The singular name `CPACK_INSTALL_SCRIPT` has existed but was not linked from the CPack documentation. Also, it supported multiple values and should have had a plural name. Add a plural-named alternative now. If both `CPACK_INSTALL_SCRIPTS` and `CPACK_INSTALL_SCRIPT` are set then ignore the latter with a warning. Signed-off-by: Alex Turbov <i.zaufi@gmail.com>
* Help: Explain interaction of cpack(1) and CPack.Joachim Wuttke (l)2018-11-151-9/+18
| | | | | | | In particular, make clear that package/installer generators are not the makefile generators of the cmake command. Also insert sections in CPack doc, and capitalize section titles.
* Help: Insert section headers in CPack moduleJoachim Wuttke (h)2018-11-121-2/+8
| | | | | The one extant section header was confusing at least: Not all the doc page is on Variables.
* Help: Replace occurrences of "Mac OS X" with "macOS"Bartosz Kosiorek2018-09-051-1/+1
| | | | | | | | Apple's main Operating system changed their name from OS X to macOS: https://www.engadget.com/2016/06/13/os-x-is-now-macos/ Revise documentation accordingly.
* CPack: Restore support for 0-valued version componentsBrad King2018-07-271-12/+15
| | | | | | | | | | | | | | In commit v3.12.0-rc1~136^2 (CPack: Use project version as default for `CPACK_PACKAGE_VERSION`, 2018-04-29) we did not account for the value of `CMAKE_PROJECT_VERSION_{MAJOR,MINOR,PATCH}` having `0`. Fix the logic to distinguish between unprovided version components and `0` components. While at it, add a test case covering the behavior described in the documentation by the original commit. The number of version components in the package name should match those provided to the `project()` command `VERSION` option. Fixes: #18199
* CPack: Add NuGet supportAlex Turbov2018-05-111-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | Create a CPack generator that uses `nuget.exe` to create packages: https://docs.microsoft.com/en-us/nuget/what-is-nuget NuGet packages could be easily produced from a `*.nuspec` file (running `nuget pack` in the directory w/ the spec file). The spec filename does not affect the result `*.nupkg` name -- only `id` and `version` elements of the spec are used (by NuGet). Some implementation details: * Minimize C++ code -- use CMake script do to the job. It just let the base class (`cmCPackGenerator`) to preinstall everything to a temp directory, render the spec file and run `nuget pack` in it, harvesting `*.nupkg` files...; * Ignore package name (and use default paths) prepared by the base class (only `CPACK_TEMPORARY_DIRECTORY` is important) -- final package filename is a responsibility of NuGet, so after generation just scan the temp directory for the result `*.nupkg` file(s) and update `packageFileNames` data-member of the generator; * The generator supports _all-in-one_ (default), _one-group-per-package_ and _one-component-per-package_ modes.
* CPack: Add more markup to module documentationAlex Turbov2018-05-081-174/+174
| | | | Also indent variable docs consistently.
* CPack: Document `CPACK_PACKAGE_DESCRIPTION` variableAlex Turbov2018-05-081-3/+11
|
* CPack: Move CPACK_BINARY_<GENNAME> with rest of docsAlex Turbov2018-05-081-10/+10
|
* CPack: Convert documentation to long-bracket comment syntaxAlex Turbov2018-05-081-320/+321
| | | | Use `#[===...==[.rst:` comments for docs.
* CPack: Fix indentationCraig Scott2018-05-041-17/+17
| | | | Addresses indentation not matching guidelines, missed in !2020. No functional changes and no changes to docs.
* Merge topic 'feature/cpack-default-package-version'Craig Scott2018-05-031-8/+45
|\ | | | | | | | | | | | | | | af1c48871c CPack: Use project version as default for `CPACK_PACKAGE_VERSION` Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Harry Mallon <hjmallon@gmail.com> Merge-request: !2020
| * CPack: Use project version as default for `CPACK_PACKAGE_VERSION`Alex Turbov2018-05-021-8/+45
| | | | | | | | | | | | | | | | | | | | * Introduce `CMAKE_PROJECT_VERSION` and the corresponsing components: `CMAKE_PROJECT_VERSION_MAJOR`, `CMAKE_PROJECT_VERSION_MINOR`, `CMAKE_PROJECT_VERSION_PATCH` and `CMAKE_PROJECT_VERSION_TWEAK`. * `CPack` module use `CMAKE_PROJECT_VERSION_MAJOR`, `CMAKE_PROJECT_VERSION_MINOR` and `CMAKE_PROJECT_VERSION_PATCH` to initialize corresponsing CPack variables.
* | Help: Improve accuracy, readability and cross-referencing of cpack docsCraig Scott2018-04-271-8/+7
|/ | | | | | This is primarily a cleanup of the cpack(1) page. The cpack.cxx file and CPack module were also updated to make the docs relating to the generator specification and option names consistent in all three places.
* CPack: Add CPACK_PACKAGE_HOMEPAGE_URL settingAlex Turbov2018-04-231-0/+12
| | | | Initialize it from `CMAKE_PROJECT_HOMEPAGE_URL`.
* CPack: Fix documented CPACK_PACKAGE_DESCRIPTION_SUMMARY defaultAlex Turbov2018-04-231-1/+1
|
* Cpack.cmake: Document some CPACK_* default valuesHarry Mallon2017-12-201-5/+6
|
* CPack: set variable commands in lower caseDomen Vrankar2017-11-191-1/+1
|
* CPack: enable setting default dir creation permissionsDomen Vrankar2017-11-081-0/+6
| | | | | | | | | | | Introduces CPACK_DEFAULT_DIRECTORY_INSTALL_PERMISSIONS variable which adds support for functionality introduced by CMAKE_DEFAULT_DIRECTORY_INSTALL_PERMISSIONS variable. Fixes #17333 # Conflicts: # Help/release/dev/cmake-default-dir-install-permissions.rst
* CPack-FreeBSD: add a generator for FreeBSD pkg(8)Adriaan de Groot2017-06-101-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds an option CPACK_ENABLE_FREEBSD_PKG to allow CPack to look for FreeBSD's libpkg / pkg(8). If this is set and the libpkg headers and library are found (which they will be, by default, on any FreeBSD system), then add a FreeBSD pkg(8) generator. The FreeBSD package tool pkg(8) uses tar.xz files (.txz) with two metadata files embedded (+MANIFEST and +COMPACT_MANIFEST). This introduces a bunch of FreeBSD-specific CPACK_FREEBSD_PACKAGE_* variables for filling in the metadata; the Debian generator does something similar. Documentation for the CPack CMake-script is styled after the Debian generator. Implementation notes: - Checks for libpkg -- the underlying implementation for pkg(8) -- and includes FreeBSD package-generation if building CMake on a UNIX host. Since libpkg can be used on BSDs, Linux and OSX, this potentially adds one more packaging format. In practice, this will only happen on FreeBSD and DragonflyBSD. - Copy-paste from cmCPackArchiveGenerator to special-case the metadata generation and to run around the internal archive generation: use libpkg instead. - Generating the metadata files is a little contrived. - Most of the validation logic for package settings is in CPackFreeBSD.cmake, as well as the code that tries to re-use packaging settings that may already be set up for Debian. - libpkg has its own notion of output filename, so we have another contrived bit of code that munges the output file list so that CPack can find the output. - Stick with C++98.
* project: Add `DESCRIPTION` parameterAlex Turbov2017-04-111-3/+13
| | | | | | | | | | | | | | | | | It is quite often the project description has used in a real world software. Examples include: * part of a help screen of the application * builtin resources (`*.rc` files, data for "About" dialog of a GUI app, & etc) * most generators for CPack can use it * it could be used by documentary software (Doxygen, Sphinx) which is usually integrated to CMake based projects via `add_custom_target()` Now `project()` call learned an optional `DESCRIPTION` parameter with a short string describing a project. Being specified, it would set the `PROJECT_DESCRIPTION` variable which could be used in `configure_file()` or whatever user wants. Also `PROJECT_DESCRIPTION` is a default value for `CPACK_PACKAGE_DESCRIPTION_SUMMARY`.
* Help: De-duplicate and spell out supported hash algorithmsBrad King2016-11-101-1/+3
| | | | | | | Spell out the supported algorithms in a definition list in the `string(<HASH>)` command documentation. Revise the `file(<HASH>)` command and CPack module documentation to reference it instead of duplicating the list.
* Simplify CMake per-source license noticesBrad King2016-09-271-13/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* CPack/RPM debuginfo packages must contain sourcesDomen Vrankar2016-09-271-0/+2
| | | | | Issue #15668 fix was missing relevant source files in debuginfo package.
* Merge topic 'cpack-rpm-srpm-package'Brad King2016-09-201-0/+5
|\ | | | | | | | | d9cec8ad CPack/RPM: Generate source rpm (SRPM) packages on demand
| * CPack/RPM: Generate source rpm (SRPM) packages on demandDomen Vrankar2016-09-201-0/+5
| | | | | | | | Closes: #15839
* | CPack: Add option to generate a checksum file next to each package filePetr Orlov2016-09-191-0/+9
|/ | | | Add variable CPACK_PACKAGE_CHECKSUM to activate it.
* Use string(APPEND) in ModulesDaniel Pfeifer2016-07-271-1/+1
| | | | | | | Automate with: find Modules -type f -print0 | xargs -0 perl -i -0pe \ 's/set\(([a-zA-Z0-9_]+)(\s+)"\$\{\1\}([^"])/string(APPEND \1\2"\3/g'
* productbuild: Add new productbuild cpack generator.Clinton Stimpson2016-06-031-0/+3
| | | | This cpack generator basically replaces the obsolete PackageMaker generator.
* CPack: Fix CPACK_OSX_SYSROOT with symbolic CMAKE_OSX_SYSROOT (#15816)Brad King2015-10-281-1/+1
| | | | | | | We support setting CMAKE_OSX_SYSROOT to a symbolic value like "macosx". Modules/Platform/Darwin-Initialize.cmake takes care of finding the actual SDK path on disk. Use that result to set CPACK_OSX_SYSROOT instead.
* Introduction of CPACK_VERBATIM_VARIABLES variableRoman Donchenko2015-09-201-8/+38
| | | | | | | | | | If variable is set to TRUE, values of all variables prefixed with CPACK_ will be escaped so special characters such as dolar sign, quotes or foreward slash will not be lost. By default variable is treated as set to FALSE for back compatibility. The cpack_encode_variables macro is changed into a function to remove scope pollution. There should be no other effects.
generated by cgit v0.12 at 2024-12-28 23:03:32 (GMT)