-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
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
Missing conanio/clang70 docker image #124
Comments
Hi @0xcccc The docker image for clang 7 is Why we don't use 70 instead? LLVM project changed the version manipulation since clang 7, so we preferred to follow the author idea to keep more authentic. There was a long discussion about it on Conan issues. We avoided to change clang 7.0 to 7 for Conan settings, because we just started to support 7 as official after to release a version with 7.0. So, to use Clang 7 we will need to set:
Regards! |
Thanks for you advice @uilianries ! I know I could set Since I'd like to build package against multiple Clang versions(e.g. |
You need to match the compiler version + docker image. If you need to build with multiple compiler versions you will need to create a job for each compiler version. If you are using some CI service, like Travis, conan provides default templates, which you can obtain by There is a better explanation about it on Conan Package Tools readme. Also, you could check most popular recipes, like zlib, to have some idea how to implement with multiple versions.
Not an extra builder, but a new build. I prefer to use add_common_builds and filter by the env vars Regards! |
Wow, that's a very detailed explanation. Thanks again @uilianries, Will definitely check it out! |
I was trying to build a package using CPT with
CONAN_CLANG_VERSIONS="7.0"
and failed:According to #54 (comment) the image is now
conanio/clang7
, so I changed the env toCONAN_CLANG_VERSIONS="7"
and ended up with another error:Seems conan use major-only for Clang >= 8.0, but not for 7.0: conan-io/conan#3643.
Environment Details
Build logs
The text was updated successfully, but these errors were encountered: