engine/1.0: Already installed! intro/1.0: Already installed! Note: Best practices As a general rule, avoid modifying or defining values for dependencies options in consumers conanfile.py. The declared global binary compatibility assumptions. The general rule is that every different value of settings and options creates a different package_id. This rule can be relaxed or expanded following different approaches: flag with linkers that supports specifying linker scripts with the -T flag, such as ld, gold, and lld. • tools.build:sysroot defines the --sysroot flag to the compiler. • tools.build:compiler_executables

engine/1.0: Already installed! intro/1.0: Already installed! Note: Best practices As a general rule, avoid modifying or defining values for dependencies options in consumers conanfile.py. The declared ([DEP]/BUILD.bazel, conan_deps_module_extension.bzl and conan_deps_repo_rules.bzl) which define the rule and all the dependencies to create/load them as Bazel repositories. The MODULE.bazel above is ready global binary compatibility assumptions. The general rule is that every different value of settings and options creates a different package_id. This rule can be relaxed or expanded following different approaches:

engine/1.0: Already installed! intro/1.0: Already installed! Note: Best practices As a general rule, avoid modifying or defining values for dependencies options in consumers conanfile.py. The declared ([DEP]/BUILD.bazel, conan_deps_module_extension.bzl and conan_deps_repo_rules.bzl) which define the rule and all the dependencies to create/load them as Bazel repositories. The MODULE.bazel above is ready global binary compatibility assumptions. The general rule is that every different value of settings and options creates a different package_id. This rule can be relaxed or expanded following different approaches:

engine/1.0: Already installed! intro/1.0: Already installed! Note: Best practices As a general rule, avoid modifying or defining values for dependencies options in consumers conanfile.py. The declared global binary compatibility assumptions. The general rule is that every different value of settings and options creates a different package_id. This rule can be relaxed or expanded following different approaches: flag with linkers that supports specifying linker scripts with the -T flag, such as ld, gold, and lld. • tools.build:sysroot defines the --sysroot flag to the compiler. • tools.build:compiler_executables

session will take place in the developers one, so the path to the sources won’t be the same. The only rule of thumb is to compile the library we want to debug in the developer machine, and thanks to Conan the "project" user The rules are evaluated in order. If the left side of the pattern matches, the rule is applied and it will not continue searching for matches. Authentication By default, Conan provides in the tool_requires attribute, the one inside the build_requirements() method will prevail. As a rule of thumb, downstream defined values always override upstream dependency values. If some tool requirement

session will take place in the developers one, so the path to the sources won’t be the same. The only rule of thumb is to compile the library we want to debug in the developer machine, and thanks to Conan the "project" user The rules are evaluated in order. If the left side of the pattern matches, the rule is applied and it will not continue searching for matches. Authentication By default, Conan provides in the tool_requires attribute, the one inside the build_requirements() method will prevail. As a rule of thumb, downstream defined values always override upstream dependency values. If some tool requirement

session will take place in the developers one, so the path to the sources won’t be the same. The only rule of thumb is to compile the library we want to debug in the developer machine, and thanks to Conan the "project" user The rules are evaluated in order. If the left side of the pattern matches, the rule is applied and it will not continue searching for matches. Authentication By default, Conan provides in the tool_requires attribute, the one inside the build_requirements() method will prevail. As a rule of thumb, downstream defined values always override upstream dependency values. If some tool requirement

session will take place in the developers one, so the path to the sources won’t be the same. The only rule of thumb is to compile the library we want to debug in the developer machine, and thanks to Conan the "project" user The rules are evaluated in order. If the left side of the pattern matches, the rule is applied and it will not continue searching for matches. 8.4. Running conan_server 109 Conan Documentation in the tool_requires attribute, the one inside the build_requirements() method will prevail. As a rule of thumb, downstream defined values always override upstream dependency values. If some tool requirement

session will take place in the developers one, so the path to the sources won’t be the same. The only rule of thumb is to compile the library we want to debug in the developer machine, and thanks to Conan the "project" user The rules are evaluated in order. If the left side of the pattern matches, the rule is applied and it will not continue searching for matches. 8.4. Running conan_server 111 Conan Documentation in the tool_requires attribute, the one inside the build_requirements() method will prevail. As a rule of thumb, downstream defined values always override upstream dependency values. If some tool requirement

session will take place in the developers one, so the path to the sources won’t be the same. The only rule of thumb is to compile the library we want to debug in the developer machine, and thanks to Conan the "project" user The rules are evaluated in order. If the left side of the pattern matches, the rule is applied and it will not continue searching for matches. 8.4. Running conan_server 109 Conan Documentation in the tool_requires attribute, the one inside the build_requirements() method will prevail. As a rule of thumb, downstream defined values always override upstream dependency values. If some tool requirement