List of environment variables required for Visual C++ to run as expected for a VS installation.
The old path where kits were stored. Upgraded in 1.1.3
The path to the user-local kits file.
Get the environment variables corresponding to a VS dev batch file.
Path to a VS environment batch file
List of arguments to pass to the batch file
Generates a string description of a kit. This is shown to the user.
The kit to generate a description for
Convert a binary (by path) to a CompilerKit. This checks if the named binary
is a GCC or Clang compiler and gets its version. If it is not a compiler,
returns null
.
Path to a binary
A CompilerKit, or null if bin
is not a known compiler
Get the kits available for a given workspace directory. Differs from
kitsForWorkspaceDirectory
in that it also returns kits declared in the
user-local kits file.
The path to a VSCode workspace directory
Get the kits declared for the given workspace directory. Looks in .vscode/cmake-kits.json
.
The path to a VSCode workspace directory
Get the path to a workspace-specific cmake-kits.json for a given worksapce directory
The directory of a workspace
Get the path to the workspace-specific cmake-kits.json for a given WorkspaceFolder object
The workspace folder
Scans a directory for compiler binaries.
Directory containing candidate binaries
A list of CompilerKits found
Search for Kits available on the platform.
A list of Kits.
Scans the system for Visual C++ installations using vswhere
Try to get a VSKit from a VS installation and architecture
A VS installation from vswhere
The architecture to try
Get a list of all Visual Studio installations available from vswhere.exe
Will not include older versions. vswhere doesn't seem to list them?
Platform arguments for VS Generators
Preferred CMake VS generators by VS version
Generated using TypeDoc
Module for controlling and working with Kits.