[Openembedded-architecture] Bringing clang to OE-Core

[Khem Raj]

> On Apr 7, 2016, at 1:39 PM, Phil Blundell <pb at pbcl.net> wrote:
> 
> On Thu, 2016-04-07 at 10:25 -0700, Khem Raj wrote:
>> There has been steady demand for clang infrastructure in OE from multiple users and developers. I have therefore opened a feature enhancement
>> request, its being used primarily in SDKs by some users. Its in good shape for most of architectures which are supported in OE-Core.
>> 
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=9417
>> 
>> to bring meta-clang into OE-core as additional compiler option.
> 
> What is the advantage of merging it into oe-core rather than maintaining
> it as a separate layer?  Are there other (existing/proposed) recipes in
> oe-core that would benefit from it?

you can benefit from using compile you want.

> 
> You mentioned that it's being used "primarily in SDKs".  How confident
> are you that everything else in oe-core is indeed compilable with clang?

most ( barring 25 odd) recipes
build fine with clang in OE-Core. I have large images with webkit and qt which
are using clang as default compiler but there are certain packages which just
don’t behave.

> 
> To be honest, my personal reaction is that if we have two compilers in
> oe-core then we're just going to have twice as many compiler bugs to
> contend with, and unless there is some very compelling win from having
> it merged I would leave it out.  But of course it's not me that makes
> the decisions.

I am just fine to maintain it as external layer, I am looking for if there is
enough interest that makes sense to move it to Core. This impacts
core piece of infrastructure and it will benefit from being closer to
that core. Not mentioning that OE-Core would become usable for clang interested
users and distros.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-architecture/attachments/20160407/39a58e09/attachment-0002.sig>