Option to disable automatic kit detection

[bharatvaj]

Is 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.

[bobbrow]

Thank you for your feature idea. We may not be able to implement it immediately, but we will track the community reactions to determine where this might fit into our backlog. We would also accept a PR from the community if anyone would be interested in helping out!

[pkral78]

+1, using Kits is proprietary, unnecessary and reinvents wheel. While someone may find it useful, it should not disturb people working with properly setup environment (using direnv or similar tools).

[bobbrow]

When we support CMakePresets.json, we may be able to disable this for repositories that have opted in to the new experience.

[syntroniks]

Kits were (and are) great. CMakePresets seems to provide a more standardized and configurable alternative.

This (writing our own kits/cmakepresets) is very helpful for specifying hand-crafted toolchain files.

For the moment, however, it is totally possible to select 'unspecified' and go from there without issue.