| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes: #24073
|
| |
|
|
|
|
| |
Issue: #24073
|
| |
|
|
|
|
| |
Fixes: #23118
|
|
|
|
|
| |
This avoids any ambiguity with whether the choices are literal
values or not. It also makes the option lines more concise.
|
| |
|
|
|
|
| |
Before it was `[file]` that AFAIK means optional.
|
|
|
|
| |
Fixes: #21031
|
|
|
|
| |
At least those involving `static_cast`.
|
|\
| |
| |
| |
| |
| |
| | |
65f7053d6c COMPILE_WARNING_AS_ERROR: Add command-line option
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7268
|
| |
| |
| |
| |
| |
| |
| | |
Add command-line option `--compile-no-warning-as-error` to ignore value of
`COMPILE_WARNING_AS_ERROR`.
Issue: #19085
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
45299a8f9b cmake: --list=presets=[type] doesn't generate incorrect warnings
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !7164
|
| |
| |
| |
| | |
Fixes #23407
|
|/
|
|
|
|
|
| |
Simplify the workflow to re-run CMake from scratch as if a build tree
were never before processed, regardless of whether it has been.
Fixes: #23119
|
|
|
|
| |
Fixes: #23224
|
|\
| |
| |
| |
| |
| |
| | |
634587e322 message: Restore explicit flushing of messages on stderr
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6913
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the `cmake` command-line tool, the `message()` command with no
message mode argument prints the message stderr using the C++ `cerr`
stream. Since commit 0a0a0f8a74 (cmMessenger: Color messages to
terminal by type, 2021-05-18, v3.21.0-rc1~146^2) and an update by
commit c7a8c9c811 (cmMessenger: Revert to non-color messages on
Windows, 2021-07-20, v3.21.1~15^2), we print the newline at the end of
the message using just `\n`. We've now observed some cases of output
on stdout and stderr getting jumbled when the two go to the same file
descriptor. Previously the newline was printed with `endl`, which
implicitly flushes. Flush explicitly to restore that behavior.
Fixes: #23155
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a `--debug-find-pkg=` option to debug find calls for specific
packages.
Add a `--debug-find-var=` option to debug find calls for specific
return variables.
Fixes: #21880
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit 0a0a0f8a74 (cmMessenger: Color messages to terminal by
type, 2021-05-18, v3.21.0-rc1~146^2) the message output no longer goes
through our custom streambuf on Windows that converts output encoding.
This can cause messages to be printed with the wrong encoding in a
Windows Console. It also causes messages to have a mix of LF and CRLF
newlines because `stderr` converts LF to CRLF but our custom streambuf
does not.
Revert to using just `cerr` for messages on Windows. Another approach
will be needed to achieve color output on Windows later.
Fixes: #22444
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Documentation added by
* commit 4f4f2028b8 (Help: Add documentation for buildPresets and
testPresets, 2021-01-13, v3.20.0-rc1~51^2~7)
* commit 676ecf0d37 (cmake-presets: Add build and test presets,
2020-12-14, v3.20.0-rc1~51^2~6)
used square brackets in the `cmake --build` signature to indicate
non-optional alternatives, which is not a typical convention.
A common convention is to use parentheses instead, but in this
case it is probably clearer to list the two signatures separately.
Fixes: #22413
|
|\
| |
| |
| |
| |
| |
| |
| | |
0a0a0f8a74 cmMessenger: Color messages to terminal by type
bceb8e2ed2 cmMessenger: Pass title inside a metadata structure
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6105
|
| |
| |
| |
| | |
Fixes: #16183
|
| | |
|
|/
|
|
|
| |
Allows us to provide better error messages when commands such as
`--target` are passed invalid input.
|
|
|
|
| |
Fixes #22186
|
|
|
|
|
|
|
| |
The main `cmake --preset` argument for configure presets supports both
forms, so support it for `cmake --build --preset` too.
Issue: #21855
|
|
|
|
|
|
| |
This form already works. Document it and add tests.
Issue: #21855
|
|
|
|
| |
Fixes: #21391
|
|
|
|
|
| |
This makes `--install` use the same parsing rules as the rest of the
the cmake executable
|
|
|
|
|
| |
This makes `--build` use the same parsing rules as the rest of the
the cmake executable
|
| |
|
|
|
|
|
|
| |
And show available options in cmake-gui.
Fixes: #21313
|
|
|
|
|
|
|
|
| |
If a path argument with no -S or -B leads to a cache directory,
use that directory as the binary directory. Otherwise, use the
binary directory from the preset.
Fixes: #21311
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
f7a5f28318 cmake: Fix '-E cat' command for binary files on Windows
90b39a5209 cmConsoleBuf: Factor out cout/cerr console buffer management
f1fdd15863 clang-format: Fix include block order in ctest.cxx and cpack.cxx
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5364
|
| |
| |
| |
| |
| |
| |
| | |
Reset `std::cout` to write in binary mode with no encoding conversions.
Co-Author: Brad King <brad.king@kitware.com>
Fixes: #21295
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixes: #21056
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
9c3beb532f cmake: Show supported formats in --help output for --profiling-format
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: dublet <github@dublet.org>
Merge-request: !5001
|
| |
| |
| | |
Fixes: #20943
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
0fddcc1e5b cmake: Tolerate nullptr from uv_default_loop
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kyle Edwards <kyle.edwards@kitware.com>
Merge-request: !4962
|
| |
| |
| |
| |
| |
| |
| | |
`uv_default_loop()` can return `nullptr` when running on a Linux kernel
configured without `CONFIG_EVENTFD`.
Fixes: #20899
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This option has been broken since commit b9f9915516 (cmMakefile: Remove
VarUsageStack., 2015-05-17, v3.3.0-rc1~52^2). That commit removed the
check that an initialized variable has actually been used and caused the
option to warn on every variable ever set. This was not caught by the
test suite because the test for the feature only checked that warnings
appear when needed and not that they do not appear when not needed.
The option was never very practical to use. Remove it to avoid the
runtime cost of usage tracking and checks for every variable (which we
were doing even when the option was not used).
|
|/
|
|
|
|
| |
provide an argument for default directory permissions in cmake --install
Fixes: #20700
|
| |
|