param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and

param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and

Adding new sub-settings). The process will be similar to: • Define new sub-setting, for instance os.distro, as explained in the section Adding new sub-settings. • Define compatibility mode, as explained 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 add to our recipes that: class Pkg(ConanFile): settings = "os", "compiler", "build_type", "arch", "distro" The value None allows for not defining it (which would be a default value, valid for all other

Adding new sub-settings). The process will be similar to: • Define new sub-setting, for instance os.distro, as explained in the section Adding new sub-settings. • Define compatibility mode, as explained 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 add to our recipes that: class Pkg(ConanFile): settings = "os", "compiler", "build_type", "arch", "distro" The value None allows for not defining it (which would be a default value, valid for all other

Adding new sub-settings). The process will be similar to: • Define new sub-setting, for instance os.distro, as explained in the section Adding new sub-settings. • Define compatibility mode, as explained 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 add to our recipes that: class Pkg(ConanFile): settings = "os", "compiler", "build_type", "arch", "distro" The value None allows for not defining it (which would be a default value, valid for all other

Adding new sub-settings). The process will be similar to: • Define new sub-setting, for instance os.distro, as explained in the section Adding new sub-settings. • Define compatibility mode, as explained 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 add to our recipes that: class Pkg(ConanFile): settings = "os", "compiler", "build_type", "arch", "distro" The value None allows for not defining it (which would be a default value, valid for all other

Adding new sub-settings). The process will be similar to: • Define new sub-setting, for instance os.distro, as explained in the section Adding new sub-settings. • Define compatibility mode, as explained 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 add to our recipes that: class Pkg(ConanFile): settings = "os", "compiler", "build_type", "arch", "distro" The value None allows for not defining it (which would be a default value, valid for all other

param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and

param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and

param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and param- eters. This is useful if, for example, the names of the packages are different from one distro or distro version to another. For example, libxcb for Apt is named libxcb-util-dev in Ubuntu >= 15.0 and