We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm migrating my project from Conan 1.59 to 2.0, and I'm getting this error because libcurl didn't upgrade to openssl/1.1.1t (used by poco).
libcurl
openssl/1.1.1t
poco
ERROR: Version conflict: libcurl/7.86.0->openssl/1.1.1s, None->openssl/1.1.1t.
Is it still possible in Conan 2.0 to override requirements in the conanfile.txt as described here for Conan 1.59?
conanfile.txt
Reading the documentation of Conan 2.0, I only see the possibility of using the override=True in the conanfile.py. [link]
override=True
conanfile.py
The text was updated successfully, but these errors were encountered:
Hi @DProvinciani
Thanks for your question.
Yes, those things are only possible in conanfile.py. We wrote a new dedicated section in the tutorial to explain this: https://docs.conan.io/2/tutorial/consuming_packages/the_flexibility_of_conanfile_py.html
If you are interested in trying, we also created a new extension command in https://github.com/conan-io/conan-extensions, for experimenting, that automatically converts conanfile.txt to conanfile.py.
Sorry, something went wrong.
Awesome! I'll give it a try.
So, considering the answer, I close the issue.
memsharded
No branches or pull requests
What is your question?
I'm migrating my project from Conan 1.59 to 2.0, and I'm getting this error because
libcurl
didn't upgrade toopenssl/1.1.1t
(used bypoco
).Is it still possible in Conan 2.0 to override requirements in the
conanfile.txt
as described here for Conan 1.59?Reading the documentation of Conan 2.0, I only see the possibility of using the
override=True
in theconanfile.py
. [link]Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: