compatibility.py Conan 2 features a new extension mechanism to define binary compatibility at a global level. A compatibility.py file in the Conan cache will be used to define which fallbacks of binaries c/b/googletest/src/gtest_ ˓→main.cc [==========] Running 1 test from 1 test suite. [----------] Global test environment set-up. [----------] 1 test from HelloTest [ RUN ] HelloTest.ComposeMessages [ ] HelloTest.ComposeMessages (0 ms) [----------] 1 test from HelloTest (0 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test suite ran. (0 ms total) [ PASSED ] 1 test

compatibility.py Conan 2 features a new extension mechanism to define binary compatibility at a global level. A compatibility.py file in the Conan cache will be used to define which fallbacks of binaries c/b/googletest/src/gtest_ ˓→main.cc [==========] Running 1 test from 1 test suite. [----------] Global test environment set-up. [----------] 1 test from HelloTest [ RUN ] HelloTest.ComposeMessages [ ] HelloTest.ComposeMessages (0 ms) [----------] 1 test from HelloTest (0 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test suite ran. (0 ms total) [ PASSED ] 1 test

compatibility.py Conan 2 features a new extension mechanism to define binary compatibility at a global level. A compatibility.py file in the Conan cache will be used to define which fallbacks of binaries c/b/googletest/src/gtest_ ˓→main.cc [==========] Running 1 test from 1 test suite. [----------] Global test environment set-up. [----------] 1 test from HelloTest [ RUN ] HelloTest.ComposeMessages [ ] HelloTest.ComposeMessages (0 ms) [----------] 1 test from HelloTest (0 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test suite ran. (0 ms total) [ PASSED ] 1 test

and build_type (Release/Debug) are some of the most common. Available settings are defined in a global settings file: ~/.conan/settings.yml. The settings for a given package are defined in the package mandatory, the rest of keyword arguments will be used to initialize the info.settings. compiler.XXX objects to calculate the correct package ID. def package_id(self): if self.settings.compiler == "Visual of the above methods: full_recipe_mode, semver_mode, etc. Note: The default_package_id_mode is a global configuration. It will change how all the package-ids are 7.6. Defining Package ABI Compatibility

compatibility.py Conan 2 features a new extension mechanism to define binary compatibility at a global level. A compatibility.py file in the Conan cache will be used to define which fallbacks of binaries c/b/googletest/src/gtest_ ˓→main.cc [==========] Running 1 test from 1 test suite. [----------] Global test environment set-up. [----------] 1 test from HelloTest [ RUN ] HelloTest.ComposeMessages [ ] HelloTest.ComposeMessages (0 ms) [----------] 1 test from HelloTest (0 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test suite ran. (0 ms total) [ PASSED ] 1 test

compatibility.py Conan 2 features a new extension mechanism to define binary compatibility at a global level. A compatibility.py file in the Conan cache will be used to define which fallbacks of binaries c/b/googletest/src/gtest_ ˓→main.cc [==========] Running 1 test from 1 test suite. [----------] Global test environment set-up. [----------] 1 test from HelloTest [ RUN ] HelloTest.ComposeMessages [ ] HelloTest.ComposeMessages (0 ms) [----------] 1 test from HelloTest (0 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test suite ran. (0 ms total) [ PASSED ] 1 test

more about the layout feature and the reference of the layout() method. Adjusting the cpp_info objects You can adjust the cpp_info in the layout method too, not only for a package in the cache, that This property only accepts list-like Python objects. All of these properties, except for cmake_file_name and cmake_module_file_name can be defined at the global cpp_info level or at the component level. explicitly declare them in Conan 1.X otherwise you can set tools.env.virtualenv:auto_use=True in the global.conf. • VirtualBuildEnv: It will generate a conanbuildenv .bat or .sh script containing environment

more about the layout feature and the reference of the layout() method. Adjusting the cpp_info objects You can adjust the cpp_info in the layout method too, not only for a package in the cache, that This property only accepts list-like Python objects. All of these properties, but cmake_file_name and cmake_module_file_name can be defined at the global cpp_info level or at the component level. The explicitly declare them in Conan 1.X otherwise you can set tools.env.virtualenv:auto_use=True in the global.conf. • VirtualBuildEnv: It will generate a conanbuildenv .bat or .sh script containing environment

more about the layout feature and the reference of the layout() method. Adjusting the cpp_info objects You can adjust the cpp_info in the layout method too, not only for a package in the cache, that This property only accepts list-like Python objects. All of these properties, but cmake_file_name and cmake_module_file_name can be defined at the global cpp_info level or at the component level. The explicitly declare them in Conan 1.X otherwise you can set tools.env.virtualenv:auto_use=True in the global.conf. • VirtualBuildEnv: It will generate a conanbuildenv .bat or .sh script containing environment

more about the layout feature and the reference of the layout() method. Adjusting the cpp_info objects You can adjust the cpp_info in the layout method too, not only for a package in the cache, that This property only accepts list-like Python objects. All of these properties, but cmake_file_name and cmake_module_file_name can be defined at the global cpp_info level or at the component level. The explicitly declare them in Conan 1.X otherwise you can set tools.env.virtualenv:auto_use=True in the global.conf. • VirtualBuildEnv: It will generate a conanbuildenv .bat or .sh script containing environment