Conan Center Index is the source index of recipes of the ConanCenter package repository for Conan.
This repository includes a Continuous Integration system that will build automatically the Conan packages for the recipes submitted via Pull Request.
Documentation
All the documentation is available in this same repository in the docs/
subfolder.
This is a list of shortcuts to some interesting topics:
- π If you want to learn how to contribute new recipes, please read docs/how_to_add_packages.md.
- π¬ FAQ: most common questions are listed in docs/faqs.md.
β οΈ The conan-center hook errors reported by CCI Bot can be found in the docs/error_knowledge_base.md.- π οΈ The internal changes related to infrastructure can be checked in docs/changelog.md.
- πΊοΈ There are various community lead initiatives which are outlined in docs/community_resources.md.
Reporting Issues
You can open issues in the issue tracker to:
-
π Report bugs/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...
- Use the
-
π‘ Request a new 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.
- Use the
-
π€ Report a 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 at [email protected]
. Thanks!