2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers and compiler version, or the computer architecture. If the package is built again from the same sources but with different settings, (e.g. for a different architecture), a new, different binary will be generated application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco --remote=conan-center Existing package recipes: (continues on next page) 11 Conan Documentation

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers and compiler version, or the computer architecture. If the package is built again from the same sources but with different settings, (e.g. for a different architecture), a new, different binary will be generated application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco --remote=conan-center Existing package recipes: (continues on next page) 11 Conan Documentation

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers and compiler version, or the computer architecture. If the package is built again from the same sources but with different settings, (e.g. for a different architecture), a new, different binary will be generated application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: (continues on next page) 11 conan Documentation

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers and compiler version, or the computer architecture. If the package is built again from the same sources but with different settings, (e.g. for a different architecture), a new, different binary will be generated application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: (continues on next page) 11 conan Documentation

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers and compiler version, or the computer architecture. If the package is built again from the same sources but with different settings, (e.g. for a different architecture), a new, different binary will be generated application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: (continues on next page) 11 conan Documentation

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers and compiler version, or the computer architecture. If the package is built again from the same sources but with different settings, (e.g. for a different architecture), a new, different binary will be generated application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: (continues on next page) 11 conan Documentation

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers and compiler version, or the computer architecture. If the package is built again from the same sources but with different settings, (e.g. for a different architecture), a new, different binary will be generated 1.21.3 $ conan search poco --remote=conan-center Existing package recipes: poco/1.8.1 poco/1.9.3 poco/1.9.4 Conan remotes must be specified in search. It will otherwise only search local cache. 3.

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers arbitrary number of binaries, one for each different platform and configuration: operating system, architecture, compiler, build type, etc. Those binaries can be created and uploaded to a server with the same 1.22.3 $ conan search poco --remote=conan-center Existing package recipes: poco/1.8.1 poco/1.9.3 poco/1.9.4 Conan remotes must be specified in search. It will otherwise only search local cache. 3.

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers arbitrary number of binaries, one for each different platform and configuration: operating system, architecture, compiler, build type, etc. Those binaries can be created and uploaded to a server with the same 1.23.0 $ conan search poco --remote=conan-center Existing package recipes: poco/1.8.1 poco/1.9.3 poco/1.9.4 Conan remotes must be specified in search. It will otherwise only search local cache. 3.

2 Decentralized package manager Conan is a decentralized package manager with a client-server architecture. This means that clients can fetch packages from, as well as upload packages to, different servers and compiler version, or the computer architecture. If the package is built again from the same sources but with different settings, (e.g. for a different architecture), a new, different binary will be generated application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: Poco/1.7.8p3@pocoproject/stable Poco/1.7.