| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| | |
ab72846794 cmake -E cat: Add ability to print standard input
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8942
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Depends on cppdap and jsoncpp.
- Add --debugger argument to enable the Debugger.
- Add --debugger-pipe argument for DAP traffics over named pipes.
- Support breakpoints by filenames and line numbers.
- Support exception breakpoints.
- Call stack shows filenames and line numbers.
- Show Cache Variables.
- Show the state of currently defined targets,
tests and directories with their properties.
- Add cmakeVersion to DAP initialize response.
- Include unit tests.
Co-authored-by: Ben McMorran <bemcmorr@microsoft.com>
|
|
|
|
|
|
|
|
|
|
| |
recommend compact, most robust signature first. So many people are
still using the multi-step pre-3.13 way of initializing a build.
Rather than simply
cmake -Bbuild
which is one step instead of 3 just to configure a new project.
|
|\
| |
| |
| |
| |
| |
| |
| | |
ef5a4d964b Deprecate "extra" generators in favor of cmake-file-api(7)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8211
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The "extra" generators were created in CMake's early years to provide
support for users of specific IDEs by directly generating their project
files alongside make or ninja files. Nowadays the file-api provides a
more generic, maintainable, well-tested, and robust way for IDEs to view
CMake project build trees. Deprecate the legacy "extra" generators to
encourage the corresponding IDEs to use the file-api.
Fixes: #19090
|
|/ |
|
| |
|
|
|
|
| |
... since CMake 3.20
|
|
|
|
| |
Fixes #21584
|
|
|
|
| |
Fixes: #23543
|
| |
|
|
|
|
|
| |
When mention execitable names use Sphinx semantic role `:program`
instead of ``executable`` or **executable**.
|
|
|
|
| |
Fixes: #24073
|
| |
|
|
|
|
|
|
|
| |
Particularly,
- options for `cmake -E env`
- options for `cmake -E tar`
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
7e6b2a92a0 try_compile: Report build dir with --debug-trycompile
cbf3252975 Tests: Remove stray debugging flag from RunCMake.CheckCompilerFlag case
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7746
|
| |
| |
| |
| |
| |
| |
| |
| | |
When `--debug-trycompile` is enabled, issue a log (with trace) for every
`try_compile` noting what directory is being used for the compilation.
This will make it easier to find the corresponding artifacts.
Closes: #24022
|
|/
|
|
|
|
| |
Define the entry point to each mode as an option for the `cmake`
program, but reference the options for that mode as part of stand-in
`cmake-<mode>` programs.
|
|
|
|
|
|
| |
Update the --debug-trycompile documentation to account for recent
changes to try_compile. Mention where in the build tree to find
artifacts when using said option.
|
|
|
|
| |
Fixes: #23118
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a8d73085f4 CPack: Add support for presets
b699610df4 cmCMakePresetsGraph: Add package presets
215b9148eb CMakePresets.json: Fix formatting of --list-presets=all
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7621
|
| |
| |
| |
| | |
Fixes: #23117
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
d0bb3286f0 cmake -E capabilities: Tell whether TLS is enabled
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !7593
|
| |
| |
| |
| | |
Fixes: #20507
|
|\ \
| |/
|/|
| |
| |
| |
| | |
536a25fedc Help: Convenient declaration for `-j, --parallel` option
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7588
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When `cmake -E env` is given the `--modify` flag, try to parse the
following argument as an `ENVIRONMENT_MODIFICATION` operation and apply
it to the environment.
This generalizes `--unset=`:
1. When implementing `ENVIRONMENT_MODIFICATION` features for other CMake
commands, the `MYVAR=OP:VALUE` strings do not need to be translated
to OP-specific flags.
2. This provides a natural and consistent extension point to introduce
new operations without introducing very many flags.
3. Users need to learn only one syntax to access the same functionality.
There is one difference between the behavior here as compared to CTest's
interpretation of the `ENVIRONMENT_MODIFICATION` test property.
The `MYVAR=reset:` command when run in `cmake -E env` will reset `MYVAR`
to whatever its value was when `cmake -E env` launched, rather than try
to checkpoint after plain `MYVAR=VALUE` options. This makes `MYVAR=VALUE`
and `--modify MYVAR=set:VALUE` semantically equivalent.
|
|
|
|
|
| |
This avoids any ambiguity with whether the choices are literal
values or not. It also makes the option lines more concise.
|
| |
|
|
|
|
| |
Similar form has already been used in the `ctest -M <mode> [-T <step>]...`
synopsis and looks quite clean w/o extra characters.
|
| |
|
|
|
|
|
| |
The form of alternative names for "placeholders" has been used already
(e.g., `<file|dir>` in the `cmake(1)` manual).
|
| |
|
|
|
|
| |
Before it was `[file]` that AFAIK means optional.
|
| |
|
| |
|
|
|
|
|
|
|
| |
It'll allow to refer to a particular option of any executable.
There are two "fake" programs added for the CMake script mode (`cmake_P`)
and CMake CLI Tool mode (`cmake_E`).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new sub-command writes a string representation of the
current log level to the output variable given to the
sub-command.
Given that the log-level might be set either via the --log-level
command line option or via the CMAKE_MESSAGE_LOG_LEVEL
cache / regular variables, the priority for each of the log level
sources is as follows, with the first one being the highest:
1) --log-level
2) CMAKE_MESSAGE_LOG_LEVEL regular variable
3) CMAKE_MESSAGE_LOG_LEVEL cache variable
4) default log level (STATUS)
Fixes: #23572
|
|\
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
0aea13d20b Help: for message(FATAL_ERROR), document nonzero exit code
cc97725137 Help: document exit code of command cmake(1)
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !7175
|
| | | |
|
| |/ |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| | |
9f1471739d cmake: Add --fresh option to clear the cache and start from scratch
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !7099
|
| |
| |
| |
| |
| |
| |
| | |
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
|