summaryrefslogtreecommitdiff
path: root/Tests/SimpleInstall/InstallScript2.cmake
Commit message (Collapse)AuthorAgeFilesLines
* Tests: Remove the SimpleInstall testKyle Edwards2018-07-171-14/+0
| | | | | The cases that were covered by SimpleInstall have been moved into RunCMake.install.
* Remove CMake-language block-end command argumentsKitware Robot2012-08-131-4/+4
| | | | | | | | | | | | | | | | | 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
* Convert CMake-language commands to lower caseKitware Robot2012-08-131-13/+13
| | | | | | | | | | | | | | | | | Ancient CMake versions required upper-case commands. Later command names became case-insensitive. Now the preferred style is lower-case. Run the following shell code: cmake --help-command-list | grep -v "cmake version" | while read c; do echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | xargs -0 sed -i -f convert.sed && rm convert.sed
* ENH: Added INSTALL(CODE) mode to allow inline specification of install ↵Brad King2006-04-121-0/+5
| | | | script code. This reduces the need for configuring an install script that needs some variable settings because the install code can set thing up first.
* ENH: Add additional subdirectory to improve testing and to allow cleanup ↵Andy Cedilnik2006-03-081-1/+1
| | | | when testing cpack
* ENH: Added INSTALL command as a placeholder for a future generic install ↵Brad King2006-02-101-0/+9
specification interface. Currently it supports only a SCRIPT option specifying a script to run during the install stage.