Repository files navigation

Conan Center Index is the source index of recipes of theConanCenter package repository forConan.

This repository includes a Continuous Integration system that will build automatically the Conan packages for the recipes submitted viaPull Request.

The current Conan Center Index CI status can be found onhttps://status.conan.io/

Any maintenance, outage or important event related to the CI will be informed there.

ConanCenter remote is configured by default in any Conan client installation. If, for any reason, you need to add it manually, just execute:

conan remote add conancenter https://center.conan.io

Starting to use recipes from this repository is as easy as runningone simple command after installing Conan:

conan install name/version@ [-g <generator>]

Of course, we really encourage you to use aconanfile.txt orconanfile.pyto list all the requirements or your project and install them all together(Conan will build a single graph and ensure congruency).

⚠️ It is very important to notice that recipes will evolve over timeand, while they are fixing some issues, they might introduce new features andimprovements, and your project can break if you upgrade them(How to prevent these breaking changes in my project?).

All the documentation is available in this same repository in thedocs/ subfolder.

This is a list of shortcuts to some interesting topics:

• 🚀 If you want to learn how tocontribute new recipes, please readdocs/adding_packages/.
• 💬FAQ: most common questions are listed indocs/faqs.md.
• ⚠️ The conan-centerhook errors reported by CCI Bot can be found in thedocs/error_knowledge_base.md.
• 🛠️ The internal changes related to infrastructure can be checked indocs/changelog.md.
• 🗺️ There are various community lead initiatives which are outlined indocs/community_resources.md.
• 🪄 To start preparing your recipes forConan 2.0, please checkdocs/v2_migration.md.

You can open issues in theissue tracker to:

• 🐛 Reportbugs/issues in a package:

  • Use the[package] tag in the title of the issue to help identifying them.
  • If you detect any issue or missing feature in a package, for example, a build failure or a recipe that not support a specific configuration.
  • Specify the name and version (zlib/1.2.11) and any relevant details about the fail configuration: Applied profile, building machine...

• 💡 Request anew library to be added:

  • Use the[request] label to search the library in the issue tracker in case the it was already requested.
  • If not, use the same[request] tag in the title of the issue to help identifying them.
  • Indicate the name and the version of the library you would like to have in the repository. Also links to the project's website,source download/repository and in general any relevant information that helps creating a recipe for it.

• 🤖 Reporta failure in the CI system:

  • If you open a Pull Request and get an unexpected error you might comment in the failing PR.
  • If the service or repository is down or failing, use the[service] tag in the title of a new issue to help identifying them.

If your issue is not appropriate for a public discussion, please contact us via e-mail atinfo@conan.io. Thanks!

All the Conan recipes in this repository are distributed under theMIT license. Thereare other files, like patches or examples used to test the packages, that could use different licenses,for those files specific license and credit must be checked in the file itself.