“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated generator will create a conanbuildinfo.cmake file that defines CMake variables as include paths and library names, that can be used in our build. Note: If you are not a CMake user, change the [generators] rately your system. • When a GCC compiler >= 5.1 is detected, the setting modeling the c++ standard library: compiler.libcxx will be set to libstdc++ that represent the old ABI compatibility for better compatibility

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated This generator creates a conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. To do so, include the generated file and add these variables Configurations. • When a GCC compiler >= 5.1 is detected, the setting modeling for the c++ standard library is set as follows: The compiler.libcxx is set to libstdc++ that represents the old ABI compatibility

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated generator will create a conanbuildinfo.cmake file that defines CMake variables as include paths and library names, that can be used in our build. Note: If you are not a CMake user, change the [generators] rately your system. • When a GCC compiler >= 5.1 is detected, the setting modeling the c++ standard library: compiler.libcxx will be set to libstdc++ that represent the old ABI compatibility for better compatibility

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated generator will create a conanbuildinfo.cmake file that defines CMake variables as include paths and library names, that can be used in our build. Note: If you are not a CMake user, change the [generators] rately your system. • When a GCC compiler >= 5.1 is detected, the setting modeling the c++ standard library: compiler.libcxx will be set to libstdc++ that represent the old ABI compatibility for better compatibility

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated generator will create a conanbuildinfo.cmake file that defines CMake variables as include paths and library names, that can be used in our build. Note: If you are not a CMake user, change the [generators] rately your system. • When a GCC compiler >= 5.1 is detected, the setting modeling the c++ standard library: compiler.libcxx will be set to libstdc++ that represent the old ABI compatibility for better compatibility

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated This generator creates a conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. Read more about Generators. 6. Next step: We are going to install Installing dependencies In Getting started we used the conan install command to download the Poco library and build an example. If you inspect the conanbuildinfo.cmake file that was created when running

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated This generator creates a conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. Read more about Generators. 6. Next step: We are going to install Installing dependencies In Getting started we used the conan install command to download the Poco library and build an example. If you inspect the conanbuildinfo.cmake file that was created when running

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated This generator creates a conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. Read more about Generators. 12 Chapter 3. Getting Started Installing dependencies In Getting started we used the conan install command to download the Poco library and build an example. If you inspect the conanbuildinfo.cmake file that was created when running

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated This generator creates a conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. Read more about Generators. 12 Chapter 3. Getting Started Installing dependencies In Getting started we used the conan install command to download the Poco library and build an example. If you inspect the conanbuildinfo.cmake file that was created when running

“binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary packages generated This generator creates a conanbuildinfo.cmake file that defines CMake variables including paths and library names that can be used in our build. Read more about Generators. 5. Next step: We are going to install Installing dependencies In Getting started we used the conan install command to download the Poco library and build an example. If you inspect the conanbuildinfo.cmake file that was created when running