integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment management Conan at all to build. ### 2.8 New package_id Conan 2 defines a new, dynamic package_id that is a great improvement over the limitations of Conan 1.X. This package_id will take into account the package application myapp. So Conan will default to a mode like full_mode that will generate a new myapp package_id, for every change in the mylib recipe or binary. While a dependency between a static library mylib_a

packages of a reference run: $ conan search poco/1.9.4@ Existing packages for recipe poco/1.9.4: Package_ID: 645aaff0a79e6036c77803601e44677556109dd9 [options] cxx_14: False enable_apacheconnector: False page) 5.1. Getting Started 35 Conan Documentation, Release 1.28.2 (continued from previous page) Package_ID: 9bfdcfa2bb925892ecf42e2a018a3f3529826676 [settings] arch: x86_64 build_type: Release compiler: a Custom package_id() The default package_id() uses the settings and options directly as defined, and assumes the semantic versioning for dependencies is defined in requires. This package_id() method can