Reference: conan
Ideal conan v2.0.6 or greater installed locally conanfile.py or conanfile.txt file present in your project conan.lock file present in your project
Requirements
Ideal
conanv2.0.6 or greater installed locallyconanfile.pyorconanfile.txtfile present in your projectconan.lockfile present in your project
Minimum
conanv2.0.6 or greater installed locallyconanfile.pyorconanfile.txtfile present in your project
Project discovery
Directories containing conanfile.py or conanfile.txt files are considered conan projects.
Analysis
From the project root, we walk through and search all directories for a conanfile.py or a conanfile.txt. Any directory which contains these files is considered a conan project. We run conan graph info -f json and convert the resulting graph into our internal represenation. An example of the graph is shown in the Conan docs.
If a conan lockfile is present, conan graph info will pick it up and give the exact versions being used in the project. If it isn't, it'll use the conanfile to figure out what the versions should be but this could be different from the actual versions depending on the constraints used. Therefore, it's recommended to have a lockfile in your project.
F.A.Q
1. Why do I need Conan v2.0.6 or greater?
This strategy uses the conan graph info command whose format was standardized in v2.0.6. Earlier formats can be supported, if required. Please reach out to the FOSSA helpdesk if you need this support.