are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it packages. For our current case, it will define our requirements (both libraries and build tools) and logic to modify options and set how we want to consume those packages. In the case of using this file to capabilities of the conanfile.py to define the project structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we

are: • The Conan client: this is a console/terminal command-line application, containing the heavy logic for package creation and consumption. Conan client has a local cache for package storage, and so it • They are more extensible and configurable. The toolchains implement most of the build system logic, leaving the build helpers, like CMake(), doing less work, and acting basically as a high level wrapper to build the logic, whereby the same build can be reused to create different packages: This can be done by defining a build_id() method in the package recipe that will specify the logic. 7.10. Packaging