functionalities and let users customize the client behavior at determined points. 12.4.1 Hook structure A hook is a Python function that will be executed at certain points of Conan workflow to customize modifying the client sources or the recipe ones. In the hooks reference you can find the full list of hook functions and exhaustive documentation about their arguments. Hooks can implement any functionality: exporting or pack- aging, or interactions with the remotes. Here is an example of a simple hook: Listing 2: example_hook.py from conans import tools def pre_export(output, conanfile, conanfile_path, reference

functionalities and let users customize the client behavior at determined points. 12.4.1 Hook structure A hook is a Python function that will be executed at certain points of Conan workflow to customize modifying the client sources or the recipe ones. In the hooks reference you can find the full list of hook functions and exhaustive documentation about their arguments. Hooks can implement any functionality: exporting or pack- aging, or interactions with the remotes. Here is an example of a simple hook: Listing 2: example_hook.py from conans import tools def pre_export(output, conanfile, conanfile_path, reference

functionalities and let users customize the client behavior at determined points. 12.4.1 Hook structure A hook is a Python function that will be executed at certain points of Conan workflow to customize modifying the client sources or the recipe ones. In the hooks reference you can find the full list of hook functions and exhaustive documentation about their arguments. Hooks can implement any functionality: exporting or pack- aging, or interactions with the remotes. Here is an example of a simple hook: Listing 2: example_hook.py from conans import tools def pre_export(output, conanfile, conanfile_path, reference

functionalities and let users customize the client behavior at determined points. 12.4.1 Hook structure A hook is a Python function that will be executed at certain points of Conan workflow to customize modifying the client sources or the recipe ones. In the hooks reference you can find the full list of hook functions and exhaustive documentation about their arguments. Hooks can implement any functionality: exporting or pack- aging, or interactions with the remotes. Here is an example of a simple hook: Listing 2: example_hook.py from conans import tools def pre_export(output, conanfile, conanfile_path, reference

functionalities and let users customize the client behavior at determined points. 12.4.1 Hook structure A hook is a Python function that will be executed at certain points of Conan workflow to customize modifying the client sources or the recipe ones. In the hooks reference you can find the full list of hook functions and exhaustive documentation about their arguments. Hooks can implement any functionality: exporting or pack- aging, or interactions with the remotes. Here is an example of a simple hook: Listing 2: example_hook.py from conans import tools def pre_export(output, conanfile, conanfile_path, reference

functionalities and let users customize the client behavior at determined points. 12.4.1 Hook structure A hook is a Python function that will be executed at certain points of Conan workflow to customize modifying the client sources or the recipe ones. In the hooks reference you can find the full list of hook functions and exhaustive documentation about their arguments. Hooks can implement any functionality: interactions with the remotes. Here is an example of a simple hook: 12.4. Hooks 173 Conan Documentation, Release 1.26.1 Listing 2: example_hook.py from conans import tools def pre_export(output, conanfile

functionalities and let users customize the client behavior at determined points. 12.3.1 Hook structure A hook is a Python function that will be executed at certain points of Conan workflow to customize modifying the client sources or the recipe ones. In the hooks reference you can find the full list of hook functions and exhaustive documentation about their arguments. Hooks can implement any functionality: exporting or pack- aging, or interactions with the remotes. Here is an example of a simple hook: Listing 1: example_hook.py from conans import tools def pre_export(output, conanfile, conanfile_path, reference

functionalities and let users customize the client behavior at determined points. 12.3.1 Hook structure A hook is a Python function that will be executed at certain points of Conan workflow to customize modifying the client sources or the recipe ones. In the hooks reference you can find the full list of hook functions and exhaustive documentation about their arguments. Hooks can implement any functionality: exporting or pack- aging, or interactions with the remotes. Here is an example of a simple hook: Listing 1: example_hook.py from conans import tools def pre_export(output, conanfile, conanfile_path, reference

it and execute it. Note that this is not necessarily intended for production. Let’s start with a hook that automatically stores as recipe metadata the test_package folder import os from conan.tools.files "*", src=folder, dst=os.path.join(conanfile.recipe_metadata_folder, "test_package")) Note that this hook doesn’t take into account that test_package can be dirty with tons of temporary build objects (it build folder and save disk space. For these cases where the build folder is not present we created a hook that copies the PDBs generated in the build folder to the package folder. This behavior can’t be forced

it and execute it. Note that this is not necessarily intended for production. Let’s start with a hook that automatically stores as recipe metadata the test_package folder import os from conan.tools.files "*", src=folder, dst=os.path.join(conanfile.recipe_metadata_folder, "test_package")) Note that this hook doesn’t take into account that test_package can be dirty with tons of temporary build objects (it build folder and save disk space. For these cases where the build folder is not present we created a hook that copies the PDBs generated in the build folder to the package folder. This behavior can’t be forced