stored in ~/.conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command line arguments, we can define a handy profile that defines them all and pass that to the command line when installing CMake commands. The CMake object just assists to translate the Conan settings to CMake command line arguments. Please note that CMake is not strictly required. You can build packages directly by invoking make

addition the --install-folder has been replaced with --output-folder. You might need to provide both arguments in Conan 1.X as some legacy generated files (conaninfo.txt, conanbuildinfo.txt, etc) are not affected cache there is a command conan list recipes . 2.2.2 Unified patterns in command arguments The arguments in Conan 1.X where we specified recipe names require now a valid reference pattern. A valid install . --build zlib/1.2.11 conan install . --build zlib/1.* • The --options and --settings arguments when used scoped: Listing 28: From: conan install . -s zlib:arch=x86 -o zlib:shared=True 28 Chapter

simple build process (the more dummy, the better), calling the build system passing some files or arguments and activating some environment launchers. This improves a lot the local development, a simple addition the --install-folder has been replaced with --output-folder. You might need to provide both arguments in Conan 1.X as some legacy generated files (conaninfo.txt, conanbuildinfo.txt, etc) are not affected cache there is a command conan list recipes . 2.2.2 Unified patterns in command arguments The arguments in Conan 1.X where we specified recipe names require now a valid reference pattern. A valid

addition the --install-folder has been replaced with --output-folder. You might need to provide both arguments in Conan 1.X as some legacy generated files (conaninfo.txt, conanbuildinfo.txt, etc) are not affected cache there is a command conan list recipes . 2.2.2 Unified patterns in command arguments The arguments in Conan 1.X where we specified recipe names require now a valid reference pattern. A valid install . --build zlib/1.2.11 conan install . --build zlib/1.* • The --options and --settings arguments when used scoped: Listing 28: From: conan install . -s zlib:arch=x86 -o zlib:shared=True 28 Chapter

stored in ~/.conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command line arguments, we can define a handy profile that defines them all and pass that to the command line when installing CMake commands. The CMake object just assists to translate the Conan settings to CMake command line arguments. Please note that CMake is not strictly required. You can build packages directly by invoking make

addition the --install-folder has been replaced with --output-folder. You might need to provide both arguments in Conan 1.X as some legacy generated files (conaninfo.txt, conanbuildinfo.txt, etc) are not affected cache there is a command conan list recipes . 2.2.2 Unified patterns in command arguments The arguments in Conan 1.X where we specified recipe names require now a valid reference pattern. A valid install . --build zlib/1.2.11 conan install . --build zlib/1.* • The --options and --settings arguments when used scoped: Listing 28: From: conan install . -s zlib:arch=x86 -o zlib:shared=True Listing

addition the --install-folder has been replaced with --output-folder. You might need to provide both arguments in Conan 1.X as some legacy generated files (conaninfo.txt, conanbuildinfo.txt, etc) are not affected cache there is a command conan list recipes . 2.2.2 Unified patterns in command arguments The arguments in Conan 1.X where we specified recipe names require now a valid reference pattern. A valid install . --build zlib/1.2.11 conan install . --build zlib/1.* • The --options and --settings arguments when used scoped: Listing 28: From: conan install . -s zlib:arch=x86 -o zlib:shared=True 28 Chapter

stored in ~/.conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command line arguments, we can define a handy profile that defines them all and pass that to the command line when installing CMake commands. The CMake object just assists to translate the Conan settings to CMake command line arguments. Please note that CMake is not strictly required. You can build packages directly by invoking make

stored in ~/.conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command line arguments, we can define a handy profile that defines them all and pass that to the command line when installing CMake commands. The CMake object just assists to translate the Conan settings to CMake command line arguments. Please note that CMake is not strictly required. You can build packages directly by invoking make

stored in ~/.conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command line arguments, we can define a handy profile that defines them all and pass that to the command line when installing CMake commands. The CMake object just assists to translate the Conan settings to CMake command line arguments. Please note that CMake is not strictly required. You can build packages directly by invoking make