generalized to any number of digits and letters, as opposed to the official “semver” that uses just 3 fields. 2.9 compatibility.py Conan 2 features a new extension mechanism to define binary compatibility computer. We can see them with: # list the binary built for the hello/1.0 package # latest is a placeholder to show the package that is the latest created $ conan list hello/1.0#:* Local Cache: hello hello/1 overrides --check-updates Check if there are recipe updates --filter FILTER Show only the specified fields --package-filter PACKAGE_FILTER Print information only for packages that match the patterns -d DEPLOYER

with conan get command: $ conan get Poco/1.9.0@pocoproject/stable To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it. The 'conan upload' command will prevent uploading recipes with 'auto' values in these␣ ˓→fields. 40 Chapter 5. Creating Packages Packages Conan Documentation, Release 1.20.5 As the warning message explains, the auto fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of

with conan get command: $ conan get Poco/1.9.0@pocoproject/stable To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it. The 'conan upload' command will prevent uploading recipes with 'auto' values in these␣ ˓→fields. 40 Chapter 5. Creating Packages Packages Conan Documentation, Release 1.19.3 As the warning message explains, the auto fields won’t be replaced unless you specify --ignore-dirty, and by default, the conan upload will block the upload of

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific with conan get command: $ conan get Poco/1.9.0@pocoproject/stable To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan 'scm.url' and 'scm.revision' auto fields. Use --ignore-dirty to force it. The 'conan upload' command will prevent uploading recipes with 'auto' values in these␣ ˓→fields. 40 Chapter 5. Creating Packages

generalized to any number of digits and letters, as opposed to the official “semver” that uses just 3 fields. 2.9 compatibility.py Conan 2 features a new extension mechanism to define binary compatibility main difference is the package_info() method. Three important things to notice: • It doesn’t define fields like self.cpp_info.libs = ["mypkg"]. Conan will not be propagating this infor- mation to the consumer that uses OSX install_name_tool utility to set @rpath��to fix the ��LC_ID_DYLIB and LC_LOAD_DYLIB fields on Apple dylibs, because it is very unusual that autotools project will manage to do this (CMake