diff options
author | Alex Reinking <alex.reinking@gmail.com> | 2022-08-14 04:42:11 -0400 |
---|---|---|
committer | Alex Reinking <alex.reinking@gmail.com> | 2022-08-17 12:54:39 -0400 |
commit | c9d70a7cc32bd023c92fd9eac19cb907b86ada8f (patch) | |
tree | 551a9588a3f1daaefc62134d892fa30ca4c1560e /Tests/RunCMake/CommandLine/E_env_modify-with-double-dash-result.txt | |
parent | 5b949bbb9114379120c29134b5effd77e39dd134 (diff) | |
download | cmake-c9d70a7cc32bd023c92fd9eac19cb907b86ada8f.tar.gz |
cmake -E env: Add --modify flag
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.
Diffstat (limited to 'Tests/RunCMake/CommandLine/E_env_modify-with-double-dash-result.txt')
-rw-r--r-- | Tests/RunCMake/CommandLine/E_env_modify-with-double-dash-result.txt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Tests/RunCMake/CommandLine/E_env_modify-with-double-dash-result.txt b/Tests/RunCMake/CommandLine/E_env_modify-with-double-dash-result.txt new file mode 100644 index 0000000000..573541ac97 --- /dev/null +++ b/Tests/RunCMake/CommandLine/E_env_modify-with-double-dash-result.txt @@ -0,0 +1 @@ +0 |