necessary values. 3. With the current package values for settings (also options and requires), it will compute a SHA1 hash that will serve as the binary package ID, e.g., c6d75a933080ca17eb7f076813e7fb21aaa740f2 generation. Within the package_id(), we have access to the self.info object, which is hashed to compute the binary ID and contains: • self.info.settings: Contains all the declared settings, always as pkg/version@user/channel#RREV:pkg_id (including the recipe revision), will be taken into account to compute the consumer package ID mypkg/1.3.4@user/testing#RREV1:73b..fa56#PREV1 => mypkg/1.3.4-a4+b3@user/

can come from the command line or profiles like –settings=build_type=Debug or –profile=debug. 2. Compute the Package ID: With the current values for settings, options, and dependencies, Conan computes a created in the server side with that time. Package revisions Package binaries when created also compute the hash of their contents, forming the package revision. But they are very different in nature to {{profile_dir}} is a jinja template expression that evaluates to the current profile folder, allowing to compute the necessary path to myvars.cmake file. The tools.cmake.cmaketoolchain:user_toolchain is a list

can come from the command line or profiles like –settings=build_type=Debug or –profile=debug. 2. Compute the Package ID: With the current values for settings, options, and dependencies, Conan computes a created in the server side with that time. Package revisions Package binaries when created also compute the hash of their contents, forming the package revision. But they are very different in nature to {{profile_dir}} is a jinja template expression that evaluates to the current profile folder, allowing to compute the necessary path to myvars.cmake file. The tools.cmake.cmaketoolchain:user_toolchain is a list

can come from the command line or profiles like –settings=build_type=Debug or –profile=debug. 2. Compute the Package ID: With the current values for settings, options, and dependencies, Conan computes a created in the server side with that time. Package revisions Package binaries when created also compute the hash of their contents, forming the package revision. But they are very different in nature to {{profile_dir}} is a jinja template expression that evaluates to the current profile folder, allowing to compute the necessary path to myvars.cmake file. The tools.cmake.cmaketoolchain:user_toolchain is a list

can come from the command line or profiles like –settings=build_type=Debug or –profile=debug. 2. Compute the Package ID: With the current values for settings, options, and dependencies, Conan computes a created in the server side with that time. Package revisions Package binaries when created also compute the hash of their contents, forming the package revision. But they are very different in nature to {{profile_dir}} is a jinja template expression that evaluates to the current profile folder, allowing to compute the necessary path to myvars.cmake file. The tools.cmake.cmaketoolchain:user_toolchain is a list

necessary values. 3. With the current package values for settings (also options and requires), it will compute a SHA1 hash that will serve as the binary package ID, e.g., c6d75a933080ca17eb7f076813e7fb21aaa740f2 generation. Within the package_id(), we have access to the self.info object, which is hashed to compute the binary ID and contains: • self.info.settings: Contains all the declared settings, always as pkg/version@user/channel#RREV:pkg_id (including the recipe revision), will be taken into account to compute the consumer package ID mypkg/1.3.4@user/testing#RREV1:73b..fa56#PREV1 => mypkg/1.3.4-a4+b3@user/

necessary values. 3. With the current package values for settings (also options and requires), it will compute a SHA1 hash that will serve as the binary package ID, e.g., c6d75a933080ca17eb7f076813e7fb21aaa740f2 generation. Within the package_id(), we have access to the self.info object, which is hashed to compute the binary ID and contains: • self.info.settings: Contains all the declared settings, always as pkg/version@user/channel#RREV:pkg_id (including the recipe revision), will be taken into account to compute the consumer package ID mypkg/1.3.4@user/testing#RREV1:73b..fa56#PREV1 => mypkg/1.3.4-a4+b3@user/

necessary values. 3. With the current package values for settings (also options and requires), it will compute a SHA1 hash that will serve as the binary package ID, e.g., c6d75a933080ca17eb7f076813e7fb21aaa740f2 generation. Within the package_id(), we have access to the self.info object, which is hashed to compute the binary ID and contains: • self.info.settings: Contains all the declared settings, always as pkg/version@user/channel#RREV:pkg_id (including the recipe revision), will be taken into account to compute the consumer package ID mypkg/1.3.4@user/testing#RREV1:73b..fa56#PREV1 => mypkg/1.3.4-a4+b3@user/

necessary values. 3. With the current package values for settings (also options and requires), it will compute a SHA1 hash that will serve as the binary package ID, e.g., c6d75a933080ca17eb7f076813e7fb21aaa740f2 generation. Within the package_id(), we have access to the self.info object, which is hashed to compute the binary ID and contains: • self.info.settings: Contains all the declared settings, always as pkg/version@user/channel#RREV:pkg_id (including the recipe revision), will be taken into account to compute the consumer package ID mypkg/1.3.4@user/testing#RREV1:73b..fa56#PREV1 => mypkg/1.3.4-a4+b3@user/

necessary values. 3. With the current package values for settings (also options and requires), it will compute a SHA1 hash that will serve as the binary package ID, e.g., c6d75a933080ca17eb7f076813e7fb21aaa740f2 generation. Within the package_id(), we have access to the self.info object, which is hashed to compute the binary ID and contains: • self.info.settings: Contains all the declared settings, always as pkg/version@user/channel#RREV of the dependencies, includ- ing the recipe revision will be taken into account to compute the consumer package ID mypkg/1.3.4@user/testing#RREV1:73b..fa56#PREV1 => mypkg/1.3.4-a4+b3@user/