see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 6.1. Installing dependencies 39 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 6.1. Installing dependencies 39 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 6.1. Installing dependencies 39 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 6.1. Installing dependencies 39 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 6.1. Installing dependencies 39 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 6.1. Installing dependencies 39 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 5.1. Installing dependencies 25 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 5.1. Installing dependencies 25 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 5.1. Installing dependencies 25 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):

see, some of the libraries end with a @ symbol followed by two strings separated by a slash. These fields are the user and channel for the Conan package, and they are useful if you want to make specific inspecting the recipe with conan get command: $ conan get poco/1.9.4@ To see only specific fields of the recipe you can use the conan inspect command instead: 4.1. Installing dependencies 23 Conan behavior in Conan v1.x) Conan will store a modified version of the conanfile.py with the values of the fields in plain text: import os from conans import ConanFile, CMake, tools class HelloConan(ConanFile):