Copy the relevant contents from to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf Alternatively, copying files and editing conan.conf can be done manually. Set up configurations: /bin # Copies all dll files from packages bin folder to my "bin" folder lib, *.dylib* -> ./bin # Copies all dylib files from packages lib folder to my "bin"␣ ˓→folder Note: You can explore the package folder profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 See also: Read more about Profiles for full reference. There is a Conan command

/bin # Copies all dll files from packages bin folder to my "bin" folder lib, *.dylib* -> ./bin # Copies all dylib files from packages lib folder to my "bin"␣ ˓→folder Note: You can explore the package folder profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 See also: Read more about Profiles for full reference. There is a Conan command build_type=Debug $ conan create . demo/testing -o hello:shared=True -s arch=x86 $ conan create . demo/testing -pr my_gcc49_debug_profile ... $ conan create ... Omitting user/channel Warning: This is an experimental

/bin # Copies all dll files from packages bin folder to my "bin" folder lib, *.dylib* -> ./bin # Copies all dylib files from packages lib folder to my "bin"␣ ˓→folder Note: You can explore the package folder profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 See also: Read more about Profiles for full reference. There is a Conan command build_type=Debug $ conan create . demo/testing -o hello:shared=True -s arch=x86 $ conan create . demo/testing -pr my_gcc49_debug_profile ... $ conan create ... Omitting user/channel Warning: This is an experimental

/bin # Copies all dll files from packages bin folder to my "bin" folder lib, *.dylib* -> ./bin # Copies all dylib files from packages lib folder to my "bin"␣ ˓→folder Note: You can explore the package folder profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 See also: Read more about Profiles for full reference. There is a Conan command build_type=Debug $ conan create . demo/testing -o hello:shared=True -s arch=x86 $ conan create . demo/testing -pr my_gcc49_debug_profile ... $ conan create ... Omitting user/channel Warning: This is an experimental

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 generate a my_launcher.sh but also will create a "conan_build.sh"␣ ˓→calling "my_launcher.sh" envvars.save_script("my_launcher") def build(self): # by default env="conanbuild" self.run("my_build_system something like: $ conan_build.sh && my_build_system.exe So the environment variable foo declared in the generate() method will be automatically passed to the my_build_system.exe. There are two generators

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 generate a my_launcher.sh but also will create a "conan_build.sh"␣ ˓→calling "my_launcher.sh" envvars.save_script("my_launcher") def build(self): # by default env="conanbuild" self.run("my_build_system something like: $ conan_build.sh && my_build_system.exe So the environment variable foo declared in the generate() method will be automatically passed to the my_build_system.exe. There are two generators

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 generate a my_launcher.sh but also will create a "conan_build.sh"␣ ˓→calling "my_launcher.sh" envvars.save_script("my_launcher") def build(self): # by default env="conanbuild" self.run("my_build_system something like: $ conan_build.sh && my_build_system.exe So the environment variable foo declared in the generate() method will be automatically passed to the my_build_system.exe. There are two generators

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 generate a my_launcher.sh but also will create a "conan_build.sh"␣ ˓→calling "my_launcher.sh" envvars.save_script("my_launcher") def build(self): # by default env="conanbuild" self.run("my_build_system something like: $ conan_build.sh && my_build_system.exe So the environment variable foo declared in the generate() method will be automatically passed to the my_build_system.exe. 2.1. Migrating the

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 generate a my_launcher.sh but also will create a "conan_build.sh"␣ ˓→calling "my_launcher.sh" envvars.save_script("my_launcher") def build(self): # by default env="conanbuild" self.run("my_build_system something like: $ conan_build.sh && my_build_system.exe So the environment variable foo declared in the generate() method will be automatically passed to the my_build_system.exe. There are two generators

import os from conan 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 generate a my_launcher.sh but also will create a "conan_build.sh"␣ ˓→calling "my_launcher.sh" envvars.save_script("my_launcher") def build(self): # by default env="conanbuild" self.run("my_build_system something like: $ conan_build.sh && my_build_system.exe So the environment variable foo declared in the generate() method will be automatically passed to the my_build_system.exe. There are two generators