file in Windows. Also, we are packaging a header file hello.h with the declaration of the library functions. The Conan package ends up with the following structure in the Conan local cache: . include hello self.conf_info.define("tools.microsoft.msbuildtoolchain:compile_options", { ˓→"ExceptionHandling": "Async"}) Conf.append(name, value) Append a value to the given configuration name. Parameters • name Release 2.0.17 (continued from previous page) warning(msg, warn_tag=None) error(msg) These output functions will only output if the verbosity level with which Conan was launched is the same or higher than

class ConsumerConan(ConanFile): python_requires = "/@/" # To use functions and␣ ˓→variables from the exported conanfile.py python_requires_extend = ".functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what

file in Windows. Also, we are packaging a header file hello.h with the declaration of the library functions. The Conan package ends up with the following structure in the Conan local cache: . include hello self.conf_info.define("tools.microsoft.msbuildtoolchain:compile_options", { ˓→"ExceptionHandling": "Async"}) Conf.append(name, value) Append a value to the given configuration name. Parameters • name Release 2.1.0 (continued from previous page) warning(msg, warn_tag=None) error(msg) These output functions will only output if the verbosity level with which Conan was launched is the same or higher than

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: attributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what

class ConsumerConan(ConanFile): python_requires = "/@/" # To use functions and␣ ˓→variables from the exported conanfile.py python_requires_extend = ".functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what

class ConsumerConan(ConanFile): python_requires = "/@/" # To use functions and␣ ˓→variables from the exported conanfile.py python_requires_extend = ".functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what

class ConsumerConan(ConanFile): python_requires = "/@/" # To use functions and␣ ˓→variables from the exported conanfile.py python_requires_extend = ".functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: attributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: attributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what

have to be replaced. The Conan 2.0 ones are in the conan package. Note the plural. • The “tools” functions are now organized in different packages, you can check the complete reference here. Listing 1: attributes are evaluated in the local directory context (see scm attribute), you can write more complex functions to retrieve the proper values, this source conanfile.py will be valid too: import os from conans changed, but without affecting the my_lib/1.0 binary for any reason (like changes consisting on new functions not used by my_lib). The same reasoning would apply if MyOtherLib was only the header. But what