class ConsumerConan(ConanFile): python_requires = "/@/" # To use functions and␣ ˓→variables from the exported conanfile.py python_requires_extend = ".functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans Studio as the input compiler (if no Visual Studio package is available). • base_compatible(): This function will transform the settings used to calculate the package ID into the “base” compiler. def package_id(self):

class ConsumerConan(ConanFile): python_requires = "/@/" # To use functions and␣ ˓→variables from the exported conanfile.py python_requires_extend = ".functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans Studio as the input compiler (if no Visual Studio package is available). • base_compatible(): This function will transform the settings used to calculate the package ID into the “base” compiler. def package_id(self):

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: capturing the coordinates, can store them in the conandata.yml using the update_conandata() helper function • The source() method can use the information in self.conan_data coming from the exported conandata cmake_build_modules The declared .build_modules come from the original package that declares useful CMake functions, variables etc. We need to use the property cmake_build_modules to declare a list of cmake files

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: capturing the coordinates, can store them in the conandata.yml using the update_conandata() helper function • The source() method can use the information in self.conan_data coming from the exported conandata cmake_build_modules The declared .build_modules come from the original package that declares useful CMake functions, variables etc. We need to use the property cmake_build_modules to declare a list of cmake files

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: capturing the coordinates, can store them in the conandata.yml using the update_conandata() helper function • The source() method can use the information in self.conan_data coming from the exported conandata cmake_build_modules The declared .build_modules come from the original package that declares useful CMake functions, variables etc. We need to use the property cmake_build_modules to declare a list of cmake files

class ConsumerConan(ConanFile): python_requires = "/@/" # To use functions and␣ ˓→variables from the exported conanfile.py python_requires_extend = ".functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans Studio as the input compiler (if no Visual Studio package is available). • base_compatible(): This function will transform the settings used to calculate the package ID into the “base” compiler. def package_id(self):

class ConsumerConan(ConanFile): python_requires = "/@/" # To use functions and␣ ˓→variables from the exported conanfile.py python_requires_extend = ".functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans Studio as the input compiler (if no Visual Studio package is available). • base_compatible(): This function will transform the settings used to calculate the package ID into the “base” compiler. def package_id(self):

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: capturing the coordinates, can store them in the conandata.yml using the update_conandata() helper function • The source() method can use the information in self.conan_data coming from the exported conandata Properties related to pkg_config, only supported by new PkgConfigDeps: • pkg_config_aliases property sets some aliases of any package/component name for the PkgConfigDeps gener- ator only, it doesn’t work

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: capturing the coordinates, can store them in the conandata.yml using the update_conandata() helper function • The source() method can use the information in self.conan_data coming from exported conandata Properties related to pkg_config, only supported by new PkgConfigDeps: • pkg_config_aliases property sets some aliases of any package/component name for the PkgConfigDeps gener- ator only, it doesn’t work

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: capturing the coordinates, can store them in the conandata.yml using the update_conandata() helper function • The source() method can use the information in self.conan_data coming from exported conandata Properties related to pkg_config, only supported by new PkgConfigDeps: • pkg_config_aliases property sets some aliases of any package/component name for the PkgConfigDeps gener- ator only, it doesn’t work