server, which should be the Conan Center server by default if the library is available. This server stores both the Conan recipes, which are the files that define how libraries must be built, and the binaries default profile was created in the first example when we run the conan profile detect command. Conan stores this file in the /profiles folder, located in the Conan user home. You can check the contents of that this is not necessarily intended for production. Let’s start with a hook that automatically stores as recipe metadata the test_package folder import os from conan.tools.files import copy def po

server, which should be the Conan Center server by default if the library is available. This server stores both the Conan recipes, which are the files that define how libraries must be built, and the binaries default profile was created in the first example when we run the conan profile detect command. Conan stores this file in the /profiles folder, located in the Conan user home. You can check the contents of that this is not necessarily intended for production. Let’s start with a hook that automatically stores as recipe metadata the test_package folder import os from conan.tools.files import copy def po

server, which should be the Conan Center server by default if the library is available. This server stores both the Conan recipes, which are the files that define how libraries must be built, and the binaries default profile was created in the first example when we run the conan profile detect command. Conan stores this file in the /profiles folder, located in the Conan user home. You can check the contents of that this is not necessarily intended for production. Let’s start with a hook that automatically stores as recipe metadata the test_package folder import os from conan.tools.files import copy def po

server, which should be the Conan Center server by default if the library is available. This server stores both the Conan recipes, which are the files that define how libraries must be built, and the binaries default profile was created in the first example when we run the conan profile detect command. Conan stores this file in the /profiles folder, located in the Conan user home. You can check the contents of that this is not necessarily intended for production. Let’s start with a hook that automatically stores as recipe metadata the test_package folder import os from conan.tools.files import copy def po

server, which should be the Conan Center server by default if the library is available. This server stores both the Conan recipes, which are the files that define how libraries must be built, and the binaries default profile was created in the first example when we run the conan profile detect command. Conan stores this file in the /profiles folder, located in the Conan user home. You can check the contents of that this is not necessarily intended for production. Let’s start with a hook that automatically stores as recipe metadata the test_package folder import os from conan.tools.files import copy def po

remote as the default, but can be changed. • If the recipe exists, the Conan client fetches and stores it in your local cache. • With the package recipe and the input settings (Linux, GCC), Conan looks Documentation, Release 1.19.3 9.4.1 Using lockfiles Lockfiles solve this problem creating a file that stores this information. In the example above, the first conan install . will generate a conan.lock file section Defining Package ABI Compatibility to get more details. self.info This self.info object stores the information that will be used to compute the package ID. This object can be manipulated to reflect

remote as the default, but can be changed. • If the recipe exists, the Conan client fetches and stores it in your local cache. • With the package recipe and the input settings (Linux, GCC), Conan looks Documentation, Release 1.20.5 9.4.1 Using lockfiles Lockfiles solve this problem creating a file that stores this information. In the example above, the first conan install . will generate a conan.lock file section Defining Package ABI Compatibility to get more details. self.info This self.info object stores the information that will be used to compute the package ID. This object can be manipulated to reflect

remote as the default, but can be changed. • If the recipe exists, the Conan client fetches and stores it in your local cache. • With the package recipe and the input settings (Linux, GCC), Conan looks configuration from a URL: $ conan config install http://url/to/some/config.zip Conan config command stores the specified URL in the conan.conf general.config_install variable. • Install the configuration section Defining Package ABI Compatibility to get more details. self.info This self.info object stores the information that will be used to compute the package ID. This object can be manipulated to reflect

remote as the default, but can be changed. • If the recipe exists, the Conan client fetches and stores it in your local cache. • With the package recipe and the input settings (Linux, GCC), Conan looks configuration from a URL: $ conan config install http://url/to/some/config.zip Conan config command stores the specified URL in the conan.conf general.config_install variable. • Install the configuration section Defining Package ABI Compatibility to get more details. self.info This self.info object stores the information that will be used to compute the package ID. This object can be manipulated to reflect

remote as the default, but can be changed. • If the recipe exists, the Conan client fetches and stores it in your local cache. • With the package recipe and the input settings (Linux, GCC), Conan looks configuration from a URL: $ conan config install http://url/to/some/config.zip Conan config command stores the specified URL in the conan.conf general.config_install variable. • Install the configuration section Defining Package ABI Compatibility to get more details. self.info This self.info object stores the information that will be used to compute the package ID. This object can be manipulated to reflect