Installing | CMake
cmake.org › installAfter copying CMake.app into /Applications (or a custom location), run it and follow the “How to Install For Command Line Use” menu item for instructions to make the command-line tools (e.g. cmake) available in the PATH. Or, one may manually add the install directory (e.g. /Applications/CMake.app/Contents/bin) to the PATH.
install — CMake 3.0.2 Documentation
https://cmake.org/cmake/help/v3.0/command/install.htmlThe FILES form specifies rules for installing files for a project. File names given as relative paths are interpreted with respect to the current source directory. Files installed by this form are by default given permissions OWNER_WRITE, OWNER_READ, GROUP_READ, and WORLD_READ if no PERMISSIONS argument is given.. The PROGRAMS form is identical to the FILES form except that …
Installing Files — Mastering CMake
cmake.org › mastering-cmake › chapterInstalling Files. ¶. Software is typically installed into a directory separate from the source and build trees. This allows it to be distributed in a clean form and isolates users from the details of the build process. CMake provides the install command to specify how a project is to be installed. This command is invoked by a project in the ...
install — CMake 3.23.0-rc4 Documentation
cmake.org › cmake › helpUse the CMAKE_INSTALL_MESSAGE variable to control which messages are printed. New in version 3.11: Many of the install () variants implicitly create the directories containing the installed files. If CMAKE_INSTALL_DEFAULT_DIRECTORY_PERMISSIONS is set, these directories will be created with the permissions specified.