Documentation, Release 1.26.1 The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 1.X versions. Recipes and packages created with these features as we are not creating a package so they are not necessary. • The package() and package_info() methods are not required since we are not creating a package. • The test() method specifies which binaries launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages Conan Documentation, Release 1.26.1 Using Conan

Documentation, Release 1.24.1 The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 1.X versions. Recipes and packages created with these features as we are not creating a package so they are not necessary. • The package() and package_info() methods are not required since we are not creating a package. • The test() method specifies which binaries launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages Conan Documentation, Release 1.24.1 Using Conan

Documentation, Release 1.25.2 The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 1.X versions. Recipes and packages created with these features as we are not creating a package so they are not necessary. • The package() and package_info() methods are not required since we are not creating a package. • The test() method specifies which binaries launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages Conan Documentation, Release 1.25.2 Using Conan

Documentation, Release 1.23.0 The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 1.X versions. Recipes and packages created with these features as we are not creating a package so they are not necessary. • The package() and package_info() methods are not required since we are not creating a package. • The test() method specifies which binaries launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages Conan Documentation, Release 1.23.0 Using Conan

Documentation, Release 1.22.3 The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 1.X versions. Recipes and packages created with these features as we are not creating a package so they are not necessary. • The package() and package_info() methods are not required since we are not creating a package. • The test() method specifies which binaries launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages Conan Documentation, Release 1.22.3 Using Conan

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 7 Examples 191 7.1 ConanFile methods examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 7.2 Conan documentation is subject to change. • The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 2.X versions. Recipes and packages created with these features new class that inherits from the ConanFile class. This class has different class attributes and methods: • settings this class attribute defines the project-wide variables, like the compiler, its version

might use different configuration. The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 1.X versions. Recipes and packages created with these features as we are not creating a package so they are not necessary. • The package() and package_info() methods are not required since we are not creating a package. • The test() method specifies which binaries launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages Conan Documentation, Release 1.20.5 Using Conan

might use different configuration. The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 1.X versions. Recipes and packages created with these features as we are not creating a package so they are not necessary. • The package() and package_info() methods are not required since we are not creating a package. • The test() method specifies which binaries launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages Conan Documentation, Release 1.21.3 Using Conan

Documentation, Release 1.42.2 The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 1.X versions. Recipes and packages created with these features recommended way to install is via pip: $ pip install conan $ pip install conan --upgrade There are other methods of installation available, including standalone installers, which don’t require a Python instal- the relevant generators. In the package recipe, this can be done using the imports() or deploy() methods. Prepare packages for use via the command line: $ conan install . -g=deploy # Copy dependencies

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 7 Examples 173 7.1 ConanFile methods examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 7.2 Conan documentation is subject to change. • The compatibility is always considered forward. New APIs, tools, methods, helpers can be added in following 2.X versions. Recipes and packages created with these features new class that inherits from the ConanFile class. This class has different class attributes and methods: • settings this class attribute defines the project-wide variables, like the compiler, its version