There has been multiple demands from developers and users to use Clang compiler with OE which is currently provided via meta-clang. This is a feature request to merge meta-clang into OE-Core in 2.2 release time frame The tools should be merged such that 1. Both compilers are available in a build where building clang is optional 2. Default remains to use gcc however a user knob is provided to switch the default to be clang. 3. Provide a knob such as TOOLCHAIN variable in global config metadata so it can be used per recipe to pin it to a particular compiler.
*** Bug 6042 has been marked as a duplicate of this bug. ***
I think that adding llvm itself might be desired by a number of people but clang as a compiler option might be a step too far for 2.2.
(In reply to comment #2) > I think that adding llvm itself might be desired by a number of people but > clang as a compiler option might be a step too far for 2.2. We can see if we can make clang as packageconfig option, I believe it will require a refactoring otherwise which could be regressive.
should we target Clang/llvm in OE-Core ?
Only llvm will be brought in in 2.3 time frame.
llvm has been committed. Clang still remains in meta-clang, move this ticket to next major release
Ross, Apparently you are interested in this...
Interested in the infrastructure but not moving the actual toolchain, yet.
(In reply to comment #8) > Interested in the infrastructure but not moving the actual toolchain, yet. I think we should discuss it more for next LTS, perhaps it would be appropriate to add it to Core.
master (will be whinlatter) now has both clang and TOOLCHAIN support. I guess the latest commit that is relevant is oe-core 45bdedd213aff8df3214b95ef2a8551c0abd93a0 (adding toolchain abstraction).