Option to disable automatic kit detection
See original GitHub issueIs it possible to add a cmake.enableKitScan: bool option?
Sometimes when giving our CMake project to new members, people often mistakenly use a scanned kit which is not configured with properties such as prefix path resulting in decreased productivity. And we are cross compiling our project to a limited number of platforms ergo unable to use the common cmake.configureArgs. It would be really convenient if this option is available.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:18 (14 by maintainers)
Top Results From Across the Web
How to Enable and Disable Automatic Workout Detection in ...
1. Open the Settings app on Apple Watch. 2. Choose General. 3. Select "Workout."
Read more >How to Disable Automatic Head Detection on AirPods Max
1. Make sure the AirPods Max headphones are connected to your iOS device. 2. Launch the Settings app on your iPhone or iPad....
Read more >How to disable Auto playback device detection. or lock it to my
Open the Settings app. · Click on Devices. · Click on AutoPlay tab. · Switch off AutoPlay.
Read more >How to Disable Auto-Detect on a Dell Monitor
Double-click on "Power," and then click on the "Power Schemes" tab. 4. Set the "Turn Off Monitor" option to "Never" to prevent Windows...
Read more >Solved: Disable auto detect column types, Is it safe? and
Solved: I fetch Data from Odata Api with the Web option and i need to handle with cells that contains letters&numbers(e.g #2345, T888),...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I fully agree that these so called automations are very annoying and in my opinion they should not be enabled by default, neither in CMake, nor in the C/C++ extension; instead, they should require an explicit action from the user to trigger them.
But unfortunately the maintainers have a different opinion. 😦
Thanks @bharatvaj. We will take a look. The idea seems fine to me, but we should leave this issue open to track the bigger issue around unnecessary scanning when presets are in use. We recently did some refactoring in this area, so we might already be most of the way there.