1. 04 Jun, 2018 1 commit
  2. 11 May, 2018 1 commit
    • Alex Turbov's avatar
      CPack: Add NuGet support · f739752a
      Alex Turbov authored
      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.
  3. 09 May, 2018 1 commit
  4. 21 Sep, 2017 1 commit
  5. 27 Mar, 2017 1 commit
  6. 23 May, 2016 1 commit
    • Domen Vrankar's avatar
      CPack/Deb possibility to change package name · adbd3985
      Domen Vrankar authored
      This patch preserves backward compatibility of
      deb package names with previous CMake versions
      but similarly to CPack/RPM allows to change
      package name format and supports DEB-DEFAULT
      setting that produces proper Debian package names.
  7. 14 May, 2016 1 commit
    • Domen Vrankar's avatar
      CPack/RPM different package names · 44ee2d71
      Domen Vrankar authored
      Packagers may now set their own rpm package
      file names or request that rpmbuild tool
      chooses one for them. It also supports handing
      of situations where one spec file may produce
      multiple rpm packages.
  8. 13 May, 2016 1 commit
  9. 01 Apr, 2016 1 commit
    • Domen Vrankar's avatar
      CPack/RPM external symlink handling · eae4eef0
      Domen Vrankar authored
      Symbolic links that point to external
      location no longer cause cmake to fail
      with string out of bounds error but
      are instead packaged as non relocatable
      symlinks and print out a warning message.
  10. 28 Mar, 2016 1 commit
    • Domen Vrankar's avatar
      cpack rpm setting of defattr · 1fe004ea
      Domen Vrankar authored
      RPM supports setting of default user, group,
      file and directory permissions that will be
      applied for files in package unless specified
      per file/dir with attr setting
      This is related to bug report 14714
  11. 12 Feb, 2016 1 commit
    • Domen Vrankar's avatar
      CPack/RPM support for upper cased component variables · 7c7efd1e
      Domen Vrankar authored
      CPACK_* variables expect component name in upper case.
      CPACK_RPM_* variables expected component name to be
      in same case as component name.
      This patch adds support for CPACK_RPM_* variables with
      upper case component names to match the convention with
      CPACK_* variables and also preserves same case component
      names for back compatibility.
  12. 25 Sep, 2015 1 commit
  13. 19 Apr, 2015 1 commit
    • Domen Vrankar's avatar
      CPackRPM content listing refactor · 76080c32
      Domen Vrankar authored
      Refactoring of content list that removes
      use of find and sed to make listing algorithm
      more clear and remove external dependencies.
      Patch also limits man pages handling to
      locations listed in brp-compress rpm script
      by default - fixes bug report #14660.
  14. 31 Mar, 2015 1 commit
    • Domen Vrankar's avatar
      CPackRPM: Add basic symlink support (#15209) · 681f3a2f
      Domen Vrankar authored
      RPM packages can contain symbolic links to relative paths - including
      support for multiple relocation paths through generation of post install
      relocation scripts.  Add basic support with limitations described in
  15. 20 Mar, 2015 1 commit
  16. 17 Mar, 2015 1 commit
    • Domen Vrankar's avatar
      CPack/RPM improved component override test · ffc1b945
      Domen Vrankar authored
      Component specific attributes test passed
      even when attribute was able to leak to
      the next component as library package is
      the last that is generated. This patch
      fixes the test as header package is generated
      in the middle so leakage causes the test to
  17. 15 Mar, 2015 2 commits
    • Domen Vrankar's avatar
      CPack/RPM architecture test fixup · 140a53a8
      Domen Vrankar authored
      Fixed architecture test that was
      missing architecture in regular
      expressions - bug was detected
      on older rpm versions where the
      check failed.
      Extended architecture test that takes
      into account older versions of rpm.
      This patch is related to 15442.
    • Domen Vrankar's avatar
      CPack/RPM relocation paths test fixup · 4552bc88
      Domen Vrankar authored
      Patch fixes bug in test reported with
      id 15442 - older versions of rpm print
      out package info a bit differently so
      we should ignore white spaces
  18. 27 Feb, 2015 2 commits
  19. 24 Feb, 2015 1 commit
    • Domen Vrankar's avatar
      CPackRPM: Drop explicit handling of '@' symbols that breaks them (#14782) · 5857ca5e
      Domen Vrankar authored
      The change in commit v2.8.12~218^2 (CPackRPM protect '@' character in
      filename processed in the spec file, 2013-07-05) was not necessary after
      commit v2.8.12~439^2 (Add support for componentized USER spec file,
      2013-04-01).  The latter replaced ${VAR} references in the spec file
      template string with \@VAR\@ references, thus protecting '@' symbols
      automatically.  This caused CPackRPM to break paths with @ symbols.
      Revert the change to fix the behavior, and add a test case.
  20. 23 Feb, 2015 1 commit
  21. 29 Jan, 2015 1 commit
  22. 21 Oct, 2014 1 commit
  23. 31 Oct, 2013 1 commit
  24. 29 Nov, 2012 1 commit
    • David Cole's avatar
      Tests: Use the right path to CPack value for running CPack tests · 587b7b6f
      David Cole authored
      These tests were not running properly on Visual Studio or
      Xcode dashboards before this commit because of the "Debug"
      or "Release" sub-directory. The scripts already have
      CMAKE_CPACK_COMMAND since the correct CMake executable is
      used to run the scripts, so just use that, rather than
      passing down an incorrect path to the CPack executable.
  25. 13 Aug, 2012 1 commit
    • Kitware Robot's avatar
      Remove CMake-language block-end command arguments · 9db31162
      Kitware Robot authored
      Ancient versions of CMake required else(), endif(), and similar block
      termination commands to have arguments matching the command starting the
      block.  This is no longer the preferred style.
      Run the following shell code:
      for c in else endif endforeach endfunction endmacro endwhile; do
          echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/'
      done >convert.sed &&
      git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' |
      egrep -z -v '^(Utilities/cm|Source/kwsys/)' |
      egrep -z -v 'Tests/CMakeTests/While-Endwhile-' |
      xargs -0 sed -i -f convert.sed &&
      rm convert.sed
  26. 30 Oct, 2011 1 commit
  27. 31 Mar, 2011 2 commits
    • Eric Noulard's avatar
      Fix #11964 Handle lib64 library on Linux · 126c993d
      Eric Noulard authored
      The AMD64 ABI document http://www.x86-64.org/documentation/abi.pdf
      does specify that 64bits binary libraries should end up in <prefix>/lib64
      and 32bits ones in <prefix>/lib. All but debian based distros do so,
      and some like OpenSUSE even enforce the rule when packaging with RPM
      and refuse to build the RPM if this is not the case.
      After some discussion (see the bug notes) we cannot do that behind
      the scene and the current fix supposes that the user shall use
      the CMAKE_INSTALL_LIBDIR variables content in its INSTALL rules if
      he wants to put the lib in the right place. CMAKE_INSTALL_LIBDIR
      shall have the appropriate value depending on the Linux distribution
      found and 32/64bitness of the host.
      The cross-compiling case (even 32bits compile on a 64bits host)
      is not handled.
    • Clinton Stimpson's avatar
  28. 23 Mar, 2011 1 commit
  29. 14 Mar, 2011 1 commit
  30. 13 Mar, 2011 1 commit
  31. 11 Mar, 2011 1 commit
  32. 10 Mar, 2011 1 commit
  33. 03 Mar, 2011 2 commits
  34. 23 Feb, 2011 1 commit
  35. 30 Jan, 2011 1 commit
  36. 14 Dec, 2010 1 commit