You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thank you for your suggestion. I have a slight feeling that I might disagree on switching to clang++ as the default compiler.
But as my experience with it is fairly limited, please give me a few insights, what benefits you think of? Iirc, the binary compatibility of libs built with either toolchain might be limited when you compile code against it using the other one....
There is always the way to provide buildflags and separate docker images for clang but that also has to bee thought through carefully due to possible size impacts on the resulting images.
Could you please share your opinions to give a better understanding of the benefits you expect from using clang over g++?
I mentioned clang because if I remember correctly, Android NDK stopped having gcc builds and only contains clang builds nowadays. Same with mac. So there is a gradual shift towards clang.
I think the libraries will be compatible with both, so you can just include both compilers in the image if you want to support this.
I have successfully compiled and run my application with both clang and g++ (outside of your docker image), using the same Qt for both. Otherwise you would need new versions of all the system libraries too.
No description provided.
The text was updated successfully, but these errors were encountered: