interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not pass in the file as a command line argument as shown in the example below: $ conan create . demo/testing -pr=clang_3.5 Continuing with the example of Poco, instead of passing in a long list of command recipes is that you don’t have to declare a requires attribute to depend on the tested hello/0.1@demo/testing package as the requires will automatically be injected by Conan during the run. However, if you choose

"requiredlib/0.1@user/stable" # Defines package requirements build_requires = "tool_a/0.2@user/testing" # Defines requirements that are␣ ˓→only used when the package is # built. These should be build␣ options.myoption1: # Specify a␣ ˓→conditional build requirement self.build_requires("zlib/1.2@user/testing") def build(self): # Responsible for␣ ˓→invoking the build system cmake = CMake(self) # Helper interchangeably. They usually denote the maturity of the package as an arbitrary string such as “stable” or “testing”, but they can be used for any purpose such as package revisions (e.g., the library version has not