Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | install(TARGETS): Add RUNTIME_DEPENDENCIES option | Kyle Edwards | 2021-06-04 | 1 | -0/+2 |
| | |||||
* | file(GET_RUNTIME_DEPENDENCIES): Add undocumented RPATH_PREFIX option | Kyle Edwards | 2021-06-04 | 1 | -1/+3 |
| | |||||
* | cmRuntimeDependencyArchive: Fix const-ness of method signatures | Kyle Edwards | 2021-06-03 | 1 | -10/+10 |
| | |||||
* | file(GET_RUNTIME_DEPENDENCIES): Add POST_{IN,EX}CLUDE_FILES arguments | Kyle Edwards | 2021-06-01 | 1 | -1/+7 |
| | |||||
* | Modernize: Use #pragma once in all header files | Kitware Robot | 2020-09-03 | 1 | -4/+1 |
| | | | | | | | | | | | | | | | | #pragma once is a widely supported compiler pragma, even though it is not part of the C++ standard. Many of the issues keeping #pragma once from being standardized (distributed filesystems, build farms, hard links, etc.) do not apply to CMake - it is easy to build CMake on a single machine. CMake also does not install any header files which can be consumed by other projects (though cmCPluginAPI.h has been deliberately omitted from this conversion in case anyone is still using it.) Finally, #pragma once has been required to build CMake since at least August 2017 (7f29bbe6 enabled server mode unconditionally, which had been using #pragma once since September 2016 (b13d3e0d)). The fact that we now require C++11 filters out old compilers, and it is unlikely that there is a compiler which supports C++11 but does not support #pragma once. | ||||
* | Revise include order using clang-format-6.0 | Kitware Robot | 2019-10-01 | 1 | -4/+4 |
| | | | | | Run the `clang-format.bash` script to update our C and C++ code to a new include order `.clang-format`. Use `clang-format` version 6.0. | ||||
* | cmFileCommand: put subcommands in unnamed namespace | Daniel Pfeifer | 2019-08-06 | 1 | -3/+3 |
| | |||||
* | IWYU: Fix handling of <memory> standard header | Brad King | 2019-07-10 | 1 | -1/+1 |
| | | | | | | | | An old workaround for `std::allocator_traits<>::value_type` lints from IWYU on `std::vector<>` usage breaks IWYU's handling of `<memory>`. Convert the workaround to use the same approach we already use for a workaround of `std::__decay_and_strip<>::::__type` lints. Then update the `<memory>` inclusions to follow the now-correct IWYU lints. | ||||
* | file: Add GET_RUNTIME_DEPENDENCIES mode | Kyle Edwards | 2019-06-10 | 1 | -0/+70 |
Co-Authored-by: Bryon Bean <bryon.bean@kitware.com> |