headers... from the right context (host vs build). To be prepared for Conan 2.0: • If you have cmake modules or cmake config files at the root of the package, it is strongly recommended to move them to a subfolder Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account for properties like cmake_target_name build_modules to 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

headers... from the right context (host vs build). To be prepared for Conan 2.0: • If you have cmake modules or cmake config files at the root of the package, it is strongly recommended to move them to a subfolder Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account for properties like cmake_target_name build_modules to 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

headers... from the right context (host vs build). To be prepared for Conan 2.0: • If you have cmake modules or cmake config files at the root of the package, it is strongly recommended to move them to a subfolder Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account for properties like cmake_target_name build_modules to 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

headers... from the right context (host vs build). To be prepared for Conan 2.0: • If you have cmake modules or cmake config files at the root of the package, it is strongly recommended to move them to a subfolder Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account for properties like cmake_target_name build_modules to 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

headers... from the right context (host vs build). To be prepared for Conan 2.0: • If you have cmake modules or cmake config files at the root of the package, it is strongly recommended to move them to a subfolder Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account for properties like cmake_target_name build_modules to 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

headers… from the right context (host vs build). To be prepared for Conan 2.0: • If you have cmake modules or cmake config files at the root of the package, it is strongly recommended to move them to a subfolder Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account for properties like cmake_target_name build_modules to 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

hook and stored in the ~/.co- nan/hooks folder. However, you can use functionalities from imported modules if you have them installed in your system or if they are installed with Conan: Listing 4: example_hook custom FindZLIB.cmake file, but the FindZLIB. cmake included in the CMake installation directory (/Modules) will locate the zlib library from the Conan package because of the CMAKE_PREFIX_PATH used by the some differences: • Only works with CMake > 3.0 • It doesn’t generate Find.cmake modules but Config. cmake/-config.cmake files. 236 Chapter 15. Integrations

hook and stored in the ~/.co- nan/hooks folder. However, you can use functionalities from imported modules if you have them installed in your system or if they are installed with Conan: Listing 4: example_hook custom FindZLIB.cmake file, but the FindZLIB. cmake included in the CMake installation directory (/Modules) will locate the zlib library from the Conan package because of the CMAKE_PREFIX_PATH used by the some differences: • Only works with CMake > 3.0 • It doesn’t generate Find.cmake modules but Config. cmake/-config.cmake files. 236 Chapter 15. Integrations

hook and stored in the ~/.co- nan/hooks folder. However, you can use functionalities from imported modules if you have them installed in your system or if they are installed with Conan: Listing 4: example_hook custom FindZLIB.cmake file, but the FindZLIB. cmake included in the CMake installation directory (/Modules) will locate the zlib library from the Conan package because of the CMAKE_PREFIX_PATH used by the some differences: • Only works with CMake > 3.0 • It doesn’t generate Find.cmake modules but Config. cmake/-config.cmake files. 238 Chapter 15. Integrations

headers... from the right context (host vs build). To be prepared for Conan 2.0: • If you have cmake modules or cmake config files at the root of the package, it is strongly recommended to move them to a subfolder Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account for properties like cmake_target_name components["mycomponent"].names["pkg_config"] = "mypkg-config-name" self.cpp_info.components["mycomponent"].build_modules.append(os.path.join("lib", (continues on next page) 2.1. Migrating the recipes 21 Conan Documentation