. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 8.2 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any by the user. 2.13.2 Command wrapper A new cmd_wrapper.py extension provides a way to wrap any conanfile.py command (i.e., anything that runs inside self.run() in a recipe), in a new command. This functionality

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 8.2 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any by the user. 2.13.2 Command wrapper A new cmd_wrapper.py extension provides a way to wrap any conanfile.py command (i.e., anything that runs inside self.run() in a recipe), in a new command. This functionality

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 8.2 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any by the user. 2.13.2 Command wrapper A new cmd_wrapper.py extension provides a way to wrap any conanfile.py command (i.e., anything that runs inside self.run() in a recipe), in a new command. This functionality

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 8.2 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any by the user. 2.13.2 Command wrapper A new cmd_wrapper.py extension provides a way to wrap any conanfile.py command (i.e., anything that runs inside self.run() in a recipe), in a new command. This functionality

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 8.2 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any by the user. 2.13.2 Command wrapper A new cmd_wrapper.py extension provides a way to wrap any conanfile.py command (i.e., anything that runs inside self.run() in a recipe), in a new command. This functionality

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 8.2 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any by the user. 2.13.2 Command wrapper A new cmd_wrapper.py extension provides a way to wrap any conanfile.py command (i.e., anything that runs inside self.run() in a recipe), in a new command. This functionality

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 12 Mastering Conan 185 12.1 Use conanfile.py for consumers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 18.3 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 12 Mastering Conan 185 12.1 Use conanfile.py for consumers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 18.3 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 8.2 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any by the user. 2.13.2 Command wrapper A new cmd_wrapper.py extension provides a way to wrap any conanfile.py command (i.e., anything that runs inside self.run() in a recipe), in a new command. This functionality

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 12 Mastering Conan 191 12.1 Use conanfile.py for consumers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 18.3 conanfile.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . package is defined by a “conanfile.py”. This is a file that defines the package’s dependencies, sources, how to build the binaries from sources, etc. One package “conanfile.py” recipe can generate any