- Oct 15, 2013
-
-
Brad King authored
This module parses its own documentation to extract supported options. Fix the indentation level to match that expected by the parser.
-
Run the convert-help.bash script to convert documentation: ./convert-help.bash "/path/to/CMake-build/bin" Then remove it.
-
Brad King authored
Create a convert-help.bash script to extract builtin documentation as reStructuredText sources in a new Help directory. Run each executable with the --help-full option targeting a .rst file to extract the documentation. Generate Sphinx "toctree" directives to point each man page at the corresponding documents it should contain. Organize cmake-commands(7), cmake-properties(7), and cmake-variables(7) man pages into sections similar to those generated by --help-properties and --help-variables output previously.
-
Run "cmake --help-full cmake.1.rst" by hand on Windows and OS X. Copy the generator/*.rst documents for generators unique to those platforms into Help/generator.
-
Brad King authored
Temporarily add a RST formatter to convert builtin documentation to .rst source files. This will be removed shortly after we use it to convert documentation. Teach the RST formatter to: * Output preformatted blocks as reStructuredText "::" literal blocks. * Output option lists as bullet lists with option names enclosed in reStructuredText ``literal`` quoting. * Output individual documentation objects (commands, variables, etc.) in separate .rst files organized in directories by type. Replace references to cmVersion::GetCMakeVersion() in builtin documentation with the literal placeholder "|release|" that will be defined as a substitution later.
-
Brad King authored
This will be replaced by alternative markup later.
-
Brad King authored
The property __CMAKE_DELETE_CACHE_CHANGE_VARS_ is not meant for public exposure.
-
Brad King authored
With our modern development workflow it is less likely a property will be added to C++ code without documentation. This mode only existed to support the DocTest which had very limited coverage of the properties anyway.
-
Brad King authored
Drop the 'documentation' build target. We will no longer use the executables to generate their own documentation. New infrastructure will be introduced later to generate documentation.
-
Brad King authored
The documentation target will be come optional, so do not reference it when it does not exist.
-
Brad King authored
Drop these tests since we will drop docbook output along with other documentation formatters.
-
Brad King authored
The latter fits more consistently with other third party integration files.
-
Brad King authored
The directory contains auxiliary support files for integration with other tools, not documentation.
-
Brad King authored
Drop the "cmake version ..." line from the top of usage and text help formats. Print it only when requested with --version or similar option.
-
Brad King authored
All the other --help-<item> options have a corresponding option --help-<item>-list. Add one for --help-policy.
-
Brad King authored
Factor the CMAKE_DATA_DIR, CMAKE_DOC_DIR, and CMAKE_MAN_DIR selection out of CMakeLists.txt and into a Source/CMakeInstallDestinations.cmake script. Load the script from the original location of the code. Cache the destination values as empty strings so we know if the user sets them explicitly. If not, then compute defaults based on the platform and full CMake version string. By not caching the versioned defaults, we can change them in a single build tree as the version changes. Remove duplication of the install destination defaults from the bootstrap script. Cache empty defaults there too. Parse from the CMake code the default values to report in the help output. Keep the CMake code in a structured format to make this reliable.
-
Brad King authored
Move logic to compute CMake_VERSION out of the top-level CMakeLists.txt file to a dedicated Source/CMakeVersionCompute.cmake module and include it from the original location. This will allow it to be re-used.
-
Brad King authored
-
eec7834e list: Fix docs for APPEND to show that elements are optional
-
2e6cadde CPackWiX: allow user supplied extra sources, objects and libraries
-
3a4a7482 CPackWiX: generate deterministic ids for directories, components and files
-
e4e5b28c cmTarget: Deprecate the LOCATION target property with a policy.
-
50762188 FindCUDA: Fix NPP library search for CUDA 5.5
-
3507d5af Deprecate COMPILE_FLAGS target property.
-
af1f6987 CMP0024: Store the fact of included export in global generator.
-
920ffbf5 Require CMake 2.8.4 or greater to build CMake
-
2e13c362 OS X: Encode -F framework search flag in per-language platform variable
-
617ee7c5 Add a test for SYSTEM headers in INTERFACE libraries.
-
This allows the use of the $<TARGET_FILE:...> generator expression as a replacement for the use of the LOCATION target property. The use of the LOCATION target property is now deprecated for in-build targets. Also drop other checks for older CMake versions: * Simplify cmake_set_target_folder macro. * Use find_package(LibArchive) unconditionally. * Simplify condition for running testVisualStudioSlnParser test. * Convert two macros to functions. * Unconditionally run the CTestTestRerunFailed test.
-
Kitware Robot authored
-
- Oct 14, 2013
-
-
list(APPEND) has been able to append nothing since commit a06dcdba (Allow LIST(APPEND) command to append nothing, 2008-01-16) but the documentation still used to imply that at least one argument is required.
-
Kitware Robot authored
-
- Oct 13, 2013
-
-
Nils Gladitz authored
-
Kitware Robot authored
-
- Oct 12, 2013
-
-
Nils Gladitz authored
-
Kitware Robot authored
-
- Oct 11, 2013
-
-
Stephen Kelly authored
The final location and name of a build-target is not determined until generate-time. However, reading the LOCATION property from a target is currently allowed at configure time. Apart from creating possibly-erroneous results, this has an impact on the implementation of cmake itself, and prevents some major cleanups from being made. Disallow reading LOCATION from build-targets with a policy. Port some existing uses of it in CMake itself to use the TARGET_FILE generator expression.
-
In CUDA 5.5 NPP was divided onto 3 separate libraries: nppc, npps, nppi.
-
Stephen Kelly authored
It is succeeded by COMPILE_OPTIONS, which supports generator expressions, is a list rather than a string, and is properly escaped.
-