can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions your pip installation matches your Python (2.7 or 3.X) version. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions your pip installation matches your Python (2.7 or 3.X) version. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions your pip installation matches your Python (2.7 or 3.X) version. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions your pip installation matches your Python (2.7 or 3.X) version. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions your pip installation matches your Python (2.7 or 3.X) version. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions your pip installation matches your Python (2.7 or 3.X) version. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions your pip installation matches your Python (2.7 or 3.X) version. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works

$ conan create . user/channel $ conan create . Pkg/0.1@user/channel $ conan create mypkgconanfile.py Pkg/0.1@user/channel $ conan export . user/channel $ conan export . Pkg/0.1@user/channel $ conan export export myfolder/myconanfile.py Pkg/0.1@user/channel This behavior aligns with the conan source, conan build, conan package commands, that all use the same argu- ments to locate the conanfile.py containing Use self.source_folder, self.build_folder, etc. in- stead • self.cpp_info, self.env_info and self.user_info scope has been reduced to only the package_info() method • gcc and ConfigureEnvironment were

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions Python (2.7 or >= 3.5) version. Python 3.4 support has been dropped. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions Python (2.7 or >= 3.5) version. Python 3.4 support has been dropped. • In Linux, you may need sudo permissions to install Conan globally. • We strongly recommend using virtualenvs (virtualenvwrapper works