1. 06 Sep, 2022 1 commit
    • Matteo Martelli's avatar
      CPack: re-use paths of tools discovered by CMakeFindBinUtils · 0c638ab5
      Matteo Martelli authored and Brad King's avatar Brad King committed
      `CMakeFindBinUtils.cmake` sets `CMAKE_<TOOL>` variables that in
      cross-compilation environments point to the toolchain specific
      executables: e.g. `CMAKE_OBJCOPY` might point to
      Pass this information to CPack.
  2. 04 Aug, 2022 1 commit
  3. 04 May, 2022 1 commit
  4. 14 Apr, 2022 1 commit
  5. 23 Feb, 2022 1 commit
  6. 22 Feb, 2022 1 commit
  7. 18 Jan, 2022 1 commit
    • Brad King's avatar
      CPack/DMG: Add explicit option to use CPACK_RESOURCE_FILE_LICENSE for SLA · 9e38bfa9
      Brad King authored
      Since macOS 12.0, the ``hdiutil udifrez`` and ``hdiutil udifderez``
      commands to embed and extract resources in a disk image are deprecated.
      The CPack DragNDrop Generator uses these to attach the SLA specified by
      the `CPACK_RESOURCE_FILE_LICENSE` option.  Since that option is shared
      by multiple CPack generators, we cannot deprecate it.  Instead, add an
      explicit option to control the behavior.  This will give projects a way
      to package on future macOS versions that remove the commands.
      In order to provide a long-term transition away from attaching SLAs to
      disk images, update `cpack` to default this behavior to OFF.  To retain
      compatibility for CMake projects, teach the CPack module to default the
      option to ON.  Later a policy can be added to change the default.
      Issue: #22978
  8. 05 Nov, 2021 1 commit
  9. 22 Apr, 2021 2 commits
  10. 26 Jan, 2021 1 commit
  11. 02 Dec, 2020 1 commit
  12. 03 Nov, 2020 1 commit
  13. 22 Jul, 2020 1 commit
    • Jean-Christophe Fillion-Robin's avatar
      Fix typos identified using codespell · 20737380
      Jean-Christophe Fillion-Robin authored and Brad King's avatar Brad King committed
      See https://github.com/codespell-project/codespell#readme
      The following command was used:
      codespell -q6 --skip="\
      " \
      -L "\
  14. 08 Jul, 2020 2 commits
  15. 15 Jun, 2020 1 commit
    • Alex Turbov's avatar
      CPack: Introduce pre- and post- build actions · 915409af
      Alex Turbov authored and Brad King's avatar Brad King committed
      and `CPACK_PACKAGE_FILES` variables.
      The first two are lists of scripts to perform
      - after pre-install files into a staging directory and before
        producing the resulting packages
      - after produsing the packages
      The post-build script(s) also get the list of actually produced
      packages in the `CPACK_PACKAGE_FILES`.
      Issue: #19077
  16. 14 Feb, 2020 1 commit
    • Joachim Wuttke's avatar
      Help: module CPack: improve summary and Introduction · 0ea52ece
      Joachim Wuttke authored and Craig Scott's avatar Craig Scott committed
      * 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
  17. 12 Feb, 2020 6 commits
  18. 31 Jan, 2020 2 commits
    • Brad King's avatar
      CPack: Deprecate OSXX11 generator · 2ed00e8e
      Brad King authored
      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
    • Brad King's avatar
      CPack: Deprecate PackageMaker generator · 7bf18749
      Brad King authored
      Xcode no longer distributes the PackageMaker tools.
      Add a deprecation warning when the generator is used.
      Issue: #20235
  19. 24 Jan, 2020 1 commit
  20. 14 Jan, 2020 1 commit
  21. 10 Jan, 2020 1 commit
  22. 11 Nov, 2019 1 commit
    • Alex Turbov's avatar
      Alex Turbov authored and Brad King's avatar Brad King committed
      In commit da5ac4bb (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
  23. 25 Oct, 2019 1 commit
  24. 30 Aug, 2019 1 commit
    • Alex Turbov's avatar
      cpack: Add `CPACK_INSTALL_CMAKE_CONFIGURATIONS` variable · da5ac4bb
      Alex Turbov authored and Brad King's avatar Brad King committed
      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.
  25. 21 Jul, 2019 1 commit
    • Alex Turbov's avatar
      CPack: Introduce CPACK_INSTALL_SCRIPTS variable · 5f966016
      Alex Turbov authored
      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's avatarAlex Turbov <i.zaufi@gmail.com>
  26. 15 Nov, 2018 1 commit
  27. 12 Nov, 2018 1 commit
  28. 05 Sep, 2018 1 commit
  29. 27 Jul, 2018 1 commit
    • Brad King's avatar
      CPack: Restore support for 0-valued version components · ed015bde
      Brad King authored
      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
  30. 11 May, 2018 1 commit
    • Alex Turbov's avatar
      CPack: Add NuGet support · f739752a
      Alex Turbov authored and Brad King's avatar Brad King committed
      Create a CPack generator that uses `nuget.exe` to create packages:
      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.
  31. 08 May, 2018 2 commits