1. 13 Jan, 2011 1 commit
    • David Cole's avatar
      Add CPACK_NSIS_INSTALL_ROOT for CMake's own installer (#9148) · 96cd1638
      David Cole authored
      Problem with CMake 2.8.4-rc1: when you launch the NSIS exe installer
      on Windows, the default install path shown to the end user is, at first,
      "\CMake 2.8".
      This problem started occurring when configuring CMake itself with an
      older CMake, after adding CPACK_NSIS_INSTALL_ROOT to fix issue 9148.
      So... it's a regression from 2.8.3.
      I forgot (again) that when you add a new CPack variable, you must
      add it to CMake's CMakeCPack.cmake file or else it is empty when
      configured with an older CMake. And on Windows, without a bootstrap
      build available, the releases are always configured with an older
      version of CMake. This may be the last time this has bitten me,
      though, because it is now burned into my brain that problems with
      CMake's installer itself are inevitably associated with adding new
      CPack variables.
      In addition to adding a definition for CPACK_NSIS_INSTALL_ROOT,
      I've gone ahead and made it differ for the 32- and 64-bit builds
      of CMake to give the end user the expected default value for the
      Program Files folder for each one.
      And, since I was adding a new 32/64 differentiator anyhow, I made
      the "NSIS package name" and "installer registry key base" different
      for 64-bit builds, too, by appending " (Win64)" to each one.
      These address the concerns mentioned in 9148's related issue:
      http://public.kitware.com/Bug/view.php?id=9094 (at least as far
      as CMake's installer is concerned). 9094 could still use a good
      general fix for all projects, though, and remains open for now.
  2. 25 Sep, 2009 2 commits
  3. 03 Sep, 2009 1 commit
  4. 20 Jul, 2009 1 commit
    • David Cole's avatar
      BUG: Add CPACK_NSIS_PACKAGE_NAME to the list of CPack variables that CMake... · 9f629f7a
      David Cole authored
      BUG: Add CPACK_NSIS_PACKAGE_NAME to the list of CPack variables that CMake overrides. We use the same value as the CPack-provided default, but do it here such that configuring with an older CMake will still give us this new variable. Necessary so that the CMake release process works with the new variable: CMake is configured with a previous CMake, but packaged with the freshly built CPack. (This fix is necessary because the fix for issue #8682 caused the side effect of having an empty CPACK_NSIS_PACKAGE_NAME for the CMake nightly package.)
  5. 26 Jun, 2009 1 commit
  6. 13 Feb, 2009 2 commits
  7. 01 Jul, 2008 1 commit
  8. 12 Mar, 2008 1 commit
  9. 18 Feb, 2008 1 commit
  10. 09 Feb, 2008 1 commit
  11. 07 Feb, 2008 1 commit
  12. 15 Jan, 2008 1 commit
  13. 26 Dec, 2007 1 commit
    • David Cole's avatar
      ENH: Give Mac installers package relocation capability. Default location is... · 764f6838
      David Cole authored
      ENH: Give Mac installers package relocation capability. Default location is still the same for backwards compatibility, but packages will now be relocatable by default like they are on Windows via the NSIS installer. New CPack variables for controlling this functionality are CPACK_PACKAGE_DEFAULT_LOCATION and CPACK_PACKAGE_RELOCATABLE.
  14. 07 Nov, 2007 1 commit
  15. 31 Oct, 2007 1 commit
  16. 30 Oct, 2007 1 commit