usually makes no sense, because we are not building any software, but it makes sense if you are cross-building software. We recommend the use of os_build and arch_build settings instead of os and arch if regular Conan settings, already present before supporting the GNU triplet convention. If you are cross-building you have to change them according to the host platform. target platform: • os target: Operating and armv7hf images with the needed packages and toolchains installed to cross build. Example: Cross-building and uploading a package along with all its missing dependencies for Linux/armv7hf is done in

FreeBSD, Solaris, and others, and it can target any platform, including desktop, server, and cross-building for embedded and bare metal devices. It integrates with other tools like Docker, MinGW, WSL, host platform where the generated binaries will run. If those platforms are different, we are cross-building software. In this section we cope with the general scenario where a library requires other tools to approach a cross-building scenario with Conan and how to use the Windows subsystems (Cygwin, MSYS2). Todo: Maybe we should divide this section, create one for the general cross-building problem and a

definition - Runtime - Conditionals - Editable packages - Protobuf modules and cross-building - CPS files location - Speeding adoption hints - Conclusions and next steps ## Problem definition - Runtime - Conditionals - Editable packages - Protobuf modules and cross-building - CPS files location - Speeding adoption hints - Conclusions and next steps ## I mplementation definition - Runtime - Conditionals - Editable packages - Protobuf modules and cross-building - CPS files location - Speeding adoption hints - Conclusions and next steps ## ZLib

Continuous Integration, isolation ..... 126 11 Systems and cross building ..... 129 11.1 Cross-building ..... 129 11.2 Windows Subsystems ..... 138 12 Extending Conan ..... 141 12.1 Customizing usually makes no sense, because we are not building any software, but it makes sense if you are cross-building software. We recommend the use of os_build and arch_build settings instead of os and arch if cross-build with Conan to any platform and the Windows subsystems (Cygwin, MSYS2). ### 11.1 Cross-building Cross-building is compiling a library or executable in one platform to be used in a different one.

cache: concurrency, Continuous Integration, isolation ..... 134 11 Systems and cross-building ..... 137 11.1 Cross-building ..... 137 11.2 Windows Subsystems ..... 146 12 Extending Conan ..... 149 usually makes no sense, because we are not building any software, but it makes sense if you are cross-building software. We recommend the use of os_build and arch_build settings instead of os and arch if cross-build with Conan to any platform and the Windows subsystems (Cygwin, MSYS2). ### 11.1 Cross-building Cross-building is compiling a library or executable in one platform to be used in a different one.

cache: concurrency, Continuous Integration, isolation ..... 134 11 Systems and cross-building ..... 137 11.1 Cross-building ..... 137 11.2 Windows Subsystems ..... 146 12 Extending Conan ..... 149 usually makes no sense, because we are not building any software, but it makes sense if you are cross-building software. We recommend the use of os_build and arch_build settings instead of os and arch if cross-build with Conan to any platform and the Windows subsystems (Cygwin, MSYS2). ### 11.1 Cross-building Cross-building is compiling a library or executable in one platform to be used in a different one.

cache: concurrency, Continuous Integration, isolation ..... 134 11 Systems and cross-building ..... 137 11.1 Cross-building ..... 137 11.2 Windows Subsystems ..... 146 12 Extending Conan ..... 149 usually makes no sense, because we are not building any software, but it makes sense if you are cross-building software. We recommend the use of os_build and arch_build settings instead of os and arch if build with Conan to any platform and the Windows subsystems (Cygwin, MSYS2). ### 11.1 Cross-building Cross-building is compiling a library or executable in one platform to be used in a different one.

concurrency, Continuous Integration, isolation 132 11 Systems and cross building 135 11.1 Cross-building 135 11.2 Windows Subsystems 144 12 Extending Conan 147 12.1 Customizing settings 147 usually makes no sense, because we are not building any software, but it makes sense if you are cross-building software. We recommend the use of os_build and arch_build settings instead of os and arch if cross-build with Conan to any platform and the Windows subsystems (Cygwin, MSYS2). ### 11.1 Cross-building Cross-building is compiling a library or executable in one platform to be used in a different one.

concurrency, Continuous Integration, isolation 132 11 Systems and cross building 135 11.1 Cross-building 135 11.2 Windows Subsystems 144 12 Extending Conan 147 12.1 Customizing settings 147 usually makes no sense, because we are not building any software, but it makes sense if you are cross-building software. We recommend the use of os_build and arch_build settings instead of os and arch if cross-build with Conan to any platform and the Windows subsystems (Cygwin, MSYS2). ### 11.1 Cross-building Cross-building is compiling a library or executable in one platform to be used in a different one.

Continuous Integration, isolation ..... 130 11 Systems and cross building ..... 133 11.1 Cross-building ..... 133 11.2 Windows Subsystems ..... 142 12 Extending Conan ..... 145 12.1 Customizing usually makes no sense, because we are not building any software, but it makes sense if you are cross-building software. We recommend the use of os_build and arch_build settings instead of os and arch if cross-build with Conan to any platform and the Windows subsystems (Cygwin, MSYS2). ### 11.1 Cross-building Cross-building is compiling a library or executable in one platform to be used in a different one.