[OE-core] [meta-clang] oe-core and meta-clang llvm coexsting?

[Khem Raj]

On 3/30/17 12:20 PM, Martin Kelly wrote:
> Hi,
> 
> I'm trying to integrate the meta-clang version of LLVM 4.0 (used for
> recipes that need a newer LLVM version) alongside the oe-core version of
> LLVM 3.3 (used for mesa). I'd like some recipes to use LLVM 4.0 and some
> to use LLVM 3.3 and for them not to collide with each other.
> 
> Right now, once the meta-clang layer is enabled, the recipes collide
> because they both provide llvm-common.bb. I tried explicitly versioning
> llvm-common, which makes them no longer collide. However, mesa then
> fails to build because the meta-clang version of LLVM installs
> llvm-config into the native common sysroot in

merging all llvm-common into a single recipe might be good

> tmp/sysroots/x86_64-linux/usr/bin/llvm-config . This llvm-config is
> based on LLVM 4.0, so when mesa picks it up, it gets confused and fails
> to build.
> 

rename llvm-config to something like llvm-config<ver>

> I'm trying to figure out the right way to fix this and get around it. Do
> you have any suggestions? I imagine there might be a quick-and-dirty way
> to do this and a nicer, long-term way to do it. I'm interested in
> hearing both.
> 
> Thanks,
> Martin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170330/fe1d1d43/attachment-0002.sig>