subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems values for Conan package recipes. It looks like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] Linux: Macos: version: [None, "10.6", "10.7", "10.8", "10.9", "10.10", "10.11", "10.12", "10.13 root of the settings.yml file, something like: os: Windows: subsystem: [None, cygwin, msys, msys2, wsl] distro: [None, RHEL6, CentOS, Debian] If we want to create different binaries from our recipes defining

cross-building for embedded and bare metal devices. It integrates with other tools like Docker, MinGW, WSL, and with all build systems such as CMake, MSBuild, Makefiles, Meson, SCons. It can even integrate config variables: • tools.microsoft.bash:subsystem: Possible values: ‘msys2’, ‘msys’, ‘cygwin’, ‘wsl’ and ‘sfu’ • tools.microsoft.bash:path (Default “bash”): Path to the shell executable. • tools.microsoft subsystems that enhance the operating system with UNIX capabilities. Conan supports MSYS2, CYGWIN, WSL and in general any subsystem that is able to run a bash shell. Many libraries use these subsystems