| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
| |
* upstream-vim-cmake-syntax:
vim-cmake-syntax 2020-10-28 (bcc3a97a)
|
| |
|
|
|
|
| |
Issue: #18870
|
|
|
|
|
|
|
| |
Add a `JOB_POOL_PRECOMPILE_HEADER` target property to specify the pool
name, and its associated `CMAKE_JOB_POOL_PRECOMPILE_HEADER` variable.
Fixes: #20217
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
09c1991895 Eclipse: Add option to set the resource encoding
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3525
|
| | |
|
|/ |
|
|
|
|
|
| |
* upstream-vim-cmake-syntax:
vim-cmake-syntax 2019-05-29 (c42ede9f)
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a9180ccf9a Tests: add a check for the Swift compiler
d745551fb6 Help: add some initial documentation for Swift support
9a182c9e5b Auxiliary: update vim syntax highlighting
e9b0063e8e Modules: add build rules for Swift Ninja support
b6412e3e38 Ninja: add placeholders to support Swift build
7d7f31161d Ninja: add support for Swift's output-file-map.json
d688c4c19d Swift: remove unnecessary unreleased Ninja infrastructure
0723582208 Swift: Detect compiler version
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3297
|
| |
| |
| |
| | |
Add new Swift keywords to the highlighting rules.
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds `Fortran_COMPILER_ID` and `Fortran_COMPILER_VERSION` generator
expression support to match equivalent `C_COMPILER_ID`,
`CXX_COMPILER_ID`, `C_COMPILER_VERSION`, and `CXX_COMPILER_VERSION`
support.
This is very helpful in the case where the C/C++ compiler suite is a
different type of compiler from the platform Fortran compiler and
projects use generator expressions to assign compiler flags and
definitions. (e.g. `GNU` C/C++ and `SunPro` Fortran on Linux)
|
|
|
|
|
|
| |
In commit v3.4.0-rc1~57^2 (Help: document CTEST_CUSTOM_* variables,
2015-09-17), the CTEST_CUSTOM_TESTS_IGNORE variable was documented with
a typo.
|
|
|
|
|
|
|
|
| |
This option only has an effect if at least one of the other LOG_<step>
options is enabled. If an error occurs for a step which has logging to
file enabled, that step's output will be printed to the console. For
cases where a large amount of output is recorded, just the end of that
output may be printed to the console.
|
|
|
|
|
|
| |
Most steps support the logging into a file but the patch command is a
notable exception. This commit adds the LOG_PATCH options that acts as
the other LOG_* options.
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some circumstances the user of ExternalProject may not desire the
split log files for stdout and stderr. In particular with a project has
many errors it can be difficult to correlate the output error with the
command that it resulted from.
This commit adds the LOG_MERGED_STDOUTERR option that when enabled
outputs into a unified <name>-<step>.log for each step. If disabled it
will default to the previous behaviour of <name>-<step>-out.log and
<name>-<step>-err.log.
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some situations it can be helpful to separate out the location of the
log files from the location of the stamp files. For instance if you have
a continuous integration that exposes the location where log files are
stored.
This commit adds an option that allows a user to override the default
behaviour of putting the log files in STAMP_DIR called LOG_DIR. The
previous behaviour of putting the log files into the STAMP_DIR applies
if LOG_DIR is not specified.
|
|
|
|
|
| |
* upstream-vim-cmake-syntax:
vim-cmake-syntax 2018-10-18 (64ff4bd7)
|
|
|
|
|
| |
* upstream-vim-cmake-syntax:
vim-cmake-syntax 2018-10-10 (ac1957fb)
|
|
|
|
|
| |
Also, added CAPTURE_CMAKE_ERROR to vim synax file for ctest_submit,
ctest_update and ctest_memcheck.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The VS_SHADER_OUTPUT_HEADER_FILE property is the name of the generated
header file containing the object code of the shader.
The VS_SHADER_VARIABLE_NAME property is the name of the variable
containing the object code in the above header file.
Signed-off-by: Kevin M. Godby <kevin@godby.org>
|
|\
| |
| |
| |
| |
| |
| |
| | |
0d543589 vim: Remove default setting of expandtab
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Maurice <m-ou.se@m-ou.se>
Merge-request: !1273
|
| |
| |
| |
| |
| |
| |
| | |
An update from vim-cmake-syntax by commit v3.9.0-rc1~167^2^2
(vim-cmake-syntax 2017-05-02, 2017-05-02) brought in a change to set
`expandtab` in CMake language files. This should be a per-project or
per-user choice instead, so drop the setting.
|
| |
| |
| |
| |
| | |
* upstream-vim-cmake-syntax:
vim-cmake-syntax 2017-08-30 (40f5f4f3)
|
| |
| |
| |
| |
| | |
The specified LABELS will be passed down to subdirectories as well as
any targets or tests in the directory.
|
| |
| |
| |
| |
| | |
Use this variable to specify a list of labels that will be reported to
CDash as subprojects.
|
| | |
|
|/
|
|
|
| |
Extend the `cmake_host_system_information()` command to add processor
identification keywords.
|
|
|
|
|
| |
* upstream-vim-cmake-syntax:
vim-cmake-syntax 2017-05-02 (15526199)
|
| |
|
|
|
|
|
|
| |
Create a `<LANG>_CPPLINT` target property (initialized by a
`CMAKE_<LANG>_CPPLINT` variable) to specify a `cpplint` style checker
command line to be run along with the compiler.
|
| |
|
| |
|
| |
|
|
* upstream-vim-cmake-syntax:
vim-cmake-syntax 2016-08-16 (e782679c)
|