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, .filenams 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

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, .filenams 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

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, .filenams 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

cache, and --update is not provided, it will fail with an error. This behavior can be change with core:allow_explicit_revision_update=True [conf] configuration. It is experimental and can result in later same dependency was possible because we used the information stored in the lockfile. Immutability A core concept of lockfiles is their immutability and the integrity of its data: Important: The information the only alternative to be both efficient and have a robust Continuous Integration of changes in our core “products” is to explictly define those “products”. In our case we will define that our products are

cache, and --update is not provided, it will fail with an error. This behavior can be change with core:allow_explicit_revision_update=True [conf] configuration. It is experimental and can result in later same dependency was possible because we used the information stored in the lockfile. Immutability A core concept of lockfiles is their immutability and the integrity of its data: Important: The information the only alternative to be both efficient and have a robust Continuous Integration of changes in our core “products” is to explictly define those “products”. In our case we will define that our products are

cache, and --update is not provided, it will fail with an error. This behavior can be change with core:allow_explicit_revision_update=True [conf] configuration. It is experimental and can result in later same dependency was possible because we used the information stored in the lockfile. Immutability A core concept of lockfiles is their immutability and the integrity of its data: Important: The information the only alternative to be both efficient and have a robust Continuous Integration of changes in our core “products” is to explictly define those “products”. In our case we will define that our products are

cache, and --update is not provided, it will fail with an error. This behavior can be change with core:allow_explicit_revision_update=True [conf] configuration. It is experimental and can result in later same dependency was possible because we used the information stored in the lockfile. Immutability A core concept of lockfiles is their immutability and the integrity of its data: Important: The information the only alternative to be both efficient and have a robust Continuous Integration of changes in our core “products” is to explictly define those “products”. In our case we will define that our products are

cache, and --update is not provided, it will fail with an error. This behavior can be change with core:allow_explicit_revision_update=True [conf] configuration. It is experimental and can result in later same dependency was possible because we used the information stored in the lockfile. Immutability A core concept of lockfiles is their immutability and the integrity of its data: Important: The information the only alternative to be both efficient and have a robust Continuous Integration of changes in our core “products” is to explictly define those “products”. In our case we will define that our products are

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657 9.2 Core guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . with either the include_prerelease option (requires = "pkg/[>1 <2, include_prerelease]"), or via the core.version_ranges:resolve_prereleases=True configuration. In this example, 1.0-pre.1 and 1.5.1-pre1 will by a few global.conf items: • core.sources:download_cache: Local path to store the sources backups to. If not set, the default Conan home cache path will be used. • core.sources:download_urls: Ordered

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617 9.2 Core guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . include_prerelease]"), or via 120 Chapter 4. Tutorial Conan Documentation, Release 2.0.17 the core.version_ranges:resolve_prereleases=True configuration. In this example, 1.0-pre.1 and 1.5.1-pre1 will by a few global.conf items: • core.sources:download_cache: Local path to store the sources backups to. If not set, the default Conan home cache path will be used. • core.sources:download_urls: Ordered