6f7edb87ea
Our upstream-built release tarballs already contain many unversioned paths and so will never overlap with another version of CMake in the same installation prefix. Therefore we do not need a versioned name for the documentation directory. Configure our release binaries to place the documentation in an unversioned directory so that one can use the same path to refer to the documentation locally even after updating CMake. For example, on OS X one may see the documentation in `/Applications/CMake.app/Contents/doc/cmake/html/index.html`. |
||
|---|---|---|
| .. | ||
| Cygwin | ||
| CMakeInstall.bmp | ||
| CMakeLogo.ico | ||
| README | ||
| cpack_wix_ui_banner.jpg | ||
| cpack_wix_ui_dialog.jpg | ||
| create-cmake-release.cmake | ||
| dash2win64_cygwin.cmake | ||
| dash2win64_release.cmake | ||
| dashmacmini2_release.cmake | ||
| dashmacmini5_release.cmake | ||
| hythloth_release.cmake | ||
| linux64_release.cmake | ||
| magrathea_release.cmake | ||
| release_cmake.cmake | ||
| release_cmake.sh.in | ||
| upload_release.cmake | ||
README
To create a cmake release, make sure the "release" tag is pointing to the expected git commit: http://cmake.org/gitweb?p=cmake.git;a=shortlog;h=refs/heads/release Then as kitware@hythloth, using an up-to-date CMake: cd ~/CMakeReleases/cmake/Utilities/Release mkdir 283rc1 cd 283rc1 ~/CMakeReleases/build/bin/cmake -DCMAKE_CREATE_VERSION=release -P ../create-cmake-release.cmake ./create-release.sh create-cmake-release.cmake: script to run to create release sh scripts Add or remove machines in create-cmake-release.cmake. Cygwin -> directory that contains cpack cygwin package files used in CMakeCPack.cmake machine_release.cmake : config files for each machine