fixed #13793 - added CLI option --{no-}analyze-all-vs-configs
#7480
Conversation
|
One of the prerequisites for #7293. |
| @@ -1605,10 +1609,22 @@ CmdLineParser::Result CmdLineParser::parseFromArgs(int argc, const char* const a | |||
| return Result::Fail; | |||
| } | |||
|
|
|||
| // TODO: conflicts with analyzeAllVsConfigs | |||
There was a problem hiding this comment.
We have like four different ways to select a Visual Studio configuration from the GUI and CLI. At least the code doing it should be unified (if possible). But something for later after the import/CLI handling has been cleaned up and has better test coverage.
There was a problem hiding this comment.
We have like four different ways to select a Visual Studio configuration from the GUI and CLI.
ouch
There was a problem hiding this comment.
so as far as I see this will not be an "official" option to start with.. i.e. not shown in the --help output.. which will make it easier to unify later.
| @@ -1605,10 +1609,22 @@ CmdLineParser::Result CmdLineParser::parseFromArgs(int argc, const char* const a | |||
| return Result::Fail; | |||
| } | |||
|
|
|||
| // TODO: conflicts with analyzeAllVsConfigs | |||
There was a problem hiding this comment.
so as far as I see this will not be an "official" option to start with.. i.e. not shown in the --help output.. which will make it easier to unify later.
No description provided.