cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs version=0.1.0 Then, we can build your project using the profile we just created: $ conan create . -pr=my_custom_profile This configuration will be passed to the conan_toolchain.cmake file, generated by

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs version=0.1.0 Then, we can build your project using the profile we just created: $ conan create . -pr=my_custom_profile This configuration will be passed to the conan_toolchain.cmake file, generated by

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs pkgconf/[*] We added Meson and pkg-config as tool requirements to the profile. By executing conan create . -pr=myprofile, those tools will be installed and made available during the package’s build process. Let’s

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs created: 7.3. Conan recipe tools examples 219 Conan Documentation, Release 2.10.1 $ conan create . -pr=my_custom_profile This configuration will be passed to the conan_toolchain.cmake file, generated by

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs system is required to run this part of the example. $ conan create . --build missing -pr:b apple-arch-x86_64 -pr:h apple-arch-armv8 ... -- Install configuration: "Release" -- Installing: /Users/myuser/

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs created: 7.3. Conan recipe tools examples 219 Conan Documentation, Release 2.9.3 $ conan create . -pr=my_custom_profile This configuration will be passed to the conan_toolchain.cmake file, generated by

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs version=0.1.0 Then, we can build your project using the profile we just created: $ conan create . -pr=my_custom_profile This configuration will be passed to the conan_toolchain.cmake file, generated by

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs version=0.1.0 Then, we can build your project using the profile we just created: $ conan create . -pr=my_custom_profile This configuration will be passed to the conan_toolchain.cmake file, generated by

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs pkgconf/[*] We added Meson and pkg-config as tool requirements to the profile. By executing conan create . -pr=myprofile, those tools will be installed and made available during the package’s build process. Let’s

cmake/3.22.6 version that runs for 64-bit architecture. $ conan install . --build missing -pr:b=default -pr:h=./profiles/raspberry Then, let’s call CMake to build the application. As we did in the previous build effectively uses the variable provided in the external myvars.cmake file: $ conan create . -pr=myprofile ... -- MY_USER_VAR1 MYVALUE1 Note that using user_toolchain while defining values for confs version=0.1.0 Then, we can build your project using the profile we just created: $ conan create . -pr=my_custom_profile This configuration will be passed to the conan_toolchain.cmake file, generated by