exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes

exist. However, if we delete it in the configure() method we can pass the option but it will have no effect. For example, if you try to pass a value to the fPIC option in Windows, Conan will raise an error evolution of lockfiles is paramount to important processes like Continuous Integration, when the effect of one change in the graph wants to be tested in isolation of other possible concurrent changes. join(conanfile.package_metadata_folder, "logs")) The usage of these hooks will have a very similar effect to the in-recipe approach: the metadata files will be created in the cache when conan create executes