git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.10.1 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.5.0 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.4.1 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.9.3 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.8.1 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.7.1 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.6.0 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.3.2 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

git $ cd examples2/tutorial/consuming_packages/simple_cmake_project We start from a very simple C language project with this structure: 19 Conan Documentation, Release 2.2.3 . CMakeLists.txt src main the case that one of them does not apply to a Conan package. We will introduce briefly how Conan models binary compatibility and how that relates to options and settings. Please, first clone the sources Remember, a “local-recipes-index” repository has limitations: it is not fully reproducible as it models only versions and not revisions, and it does not provide binaries. Therefore, outside of these cases

build files . . . . . . . . . . . . . . . . . . . . . . . . . 366 17.23 How to use Conan as other language package manager . . . . . . . . . . . . . . . . . . . . . . . . . 367 17.24 How to manage SSL (TLS) binary compatibility can even be configured and customized on a per-package basis. Conan has a very large and active community, especially in Github repositories and Slack #conan channel. This com- munity conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way