Open guochengli opened 4 years ago
It looks like we log the arguments for legacy and file-api modes, but not CMake Server mode. If you are able to upgrade your CMake binary to 3.15 or newer, you should see the configure arguments when you enable the "cmake.loggingLevel": "debug"
setting.
You're right. My cmake version is 3.10 and I don't have the permission to upgrade it, unfortunately. It looks like I need to wait till I'm the boss :)
This issue is now marked as 'stale-old' due to there being no activity on it for the past 720 days. Unless the 'stale-old' label is removed or the issue is commented on, this will be remain open for at least 14 days and then it may be closed. If you would like to make this issue exempt from getting stale, please add the 'stale-exempt' label.
Issue Type: Feature Request
Currently after I run CMake/Configure for c++ project, I can't find the underlying cmake configure command in 'OUTPUT' window. Whereas cmake build command can be printed in 'OUTPUT' window if I trigger cmake build. For several times I need to know what exact cmake 'configure' command was generated. Is there any place I can find the generated cmake configure command? Or may I suggest to add this to the 'OUTPUT' window at the initial cmake configuring stage? Sincerely.
Extension version: 1.4.0 VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z) OS version: Windows_NT x64 10.0.18363 Remote OS version: Linux x64 4.15.0-1050-oem