correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt) recipe to declare “Visual Studio” as a default compiler because that is something defined by the end consumer, and unlikely to make sense if they are working in Linux. On the other hand, options are intended package_info() methods of all dependencies will be called and gathered so you can generate files for the consumer build system, as the conanbuildinfo.cmake for the cmake generator. Also the imports feature will

correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt) recipe to declare “Visual Studio” as a default compiler because that is something defined by the end consumer, and unlikely to make sense if they are working in Linux. On the other hand, options are intended package_info() methods of all dependencies will be called and gathered so you can generate files for the consumer build system, as the conanbuildinfo.cmake for the cmake generator. Also the imports feature will

correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt) recipe to declare “Visual Studio” as a default compiler because that is something defined by the end consumer, and unlikely to make sense if they are working in Linux. On the other hand, options are intended package_info() methods of all dependencies will be called and gathered so you can generate files for the consumer build system, as the conanbuildinfo.cmake for the cmake generator. Also the imports feature will

correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt) recipe to declare “Visual Studio” as a default compiler because that is something defined by the end consumer, and unlikely to make sense if they are working in Linux. On the other hand, options are intended build folder to the final package folder. • Finally, the package_info() method defines that the consumer must link with the “hello” library when using this package. Other information as include or lib

correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt) recipe to declare “Visual Studio” as a default compiler because that is something defined by the end consumer, and unlikely to make sense if they are working in Linux. On the other hand, options are intended build folder to the final package folder. • Finally, the package_info() method defines that the consumer must link with the “hello” library when using this package. Other information as include or lib

version = "1.0" def package_info(self): self.conf_info.define("user.myconf:foo", "bar") In a consumer recipe: import os from conans import ConanFile class Pkg(ConanFile): requires = "pkg/1.0" def generate(self): my_value = self.dependencies[pkg].conf_info.get("user.myconf:foo") ... Note: The consumer recipes will have a self.conf object available with the aggregated configuration from all the recipes correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt)

version = "1.0" def package_info(self): self.conf_info.define("user.myconf:foo", "bar") In a consumer recipe: import os from conans import ConanFile class Pkg(ConanFile): requires = "pkg/1.0" def generate(self): my_value = self.dependencies[pkg].conf_info.get("user.myconf:foo") ... Note: The consumer recipes will have a self.conf object available with the aggregated configuration from all the recipes correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt)

correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt) recipe to declare “Visual Studio” as a default compiler because that is something defined by the end consumer, and unlikely to make sense if they are working in Linux. On the other hand, options are intended build folder to the final package folder. • Finally, the package_info() method defines that the consumer must link with the “hello” library when using this package. Other information as include or lib

minor_mode mode. In Conan 2, the one doing modifications to mylib_a can better express whether the consumer mylib_b needs to rebuild or not, based on the version bump (patch version bump will not trigger already installed system-wide? Conan can also help you install these tools and use them to compile consumer projects or other Conan packages. In this case, you can declare this dependency in Conan using a package to declare “Visual Studio” as a default compiler because that is something defined by the end consumer, and unlikely to make sense if they are working in Linux. • options are intended for package-specific

correctly. Run the following command in your console: $ conan The response should be similar to: Consumer commands install Installs the requirements specified in a recipe (conanfile.py or conanfile. ˓→txt) recipe to declare “Visual Studio” as a default compiler because that is something defined by the end consumer, and unlikely to make sense if they are working in Linux. On the other hand, options are intended package_info() methods of all dependencies will be called and gathered so you can generate files for the consumer build system, as the conanbuildinfo.cmake for the cmake generator. Also the imports feature will