1. Yocto
  2. Topics

#yocto llvm support #yocto

Monsees, Steven C (US)
 

 

Under ../poky/meta/recipes-devtools the is “llvm”…

 

Devtool search <component>

Devtool sdk-install <component>

 

Will add this component to my EXT SDK…

 

Is this a fully functional llvm drop ?,

(i.e. is it compatible with meta-clang?, and can I use them together to build 3rd party extensions for my platform ?)

 

Is it better to add supported components this way rather than building them in directly to EXT SDK ?

 

Thanks,

Steve
Anton Antonov
 

Hi Steven,

  I used meta-clang in my recipes and I noticed that:
1. The current release of poky uses LLVM v11.1.0 by default (poky/meta/recipes-devtools/llvm/llvm_git.bb)
2. Meta-clang requires LLVM v12.0.0 (meta-clang/conf/layer.conf defines LLVMVERSION = "12.0.0")

As a result just including meta-clang into bblayers.conf will require bitbake to build a new version of LLVM and rebuild everything which uses it

Anton
Monsees, Steven C (US)
 

 

I noticed similar behavior…

 

I am running zeus 3.0.4, “devtool sdk-install llvm” will get llvm 8.0.1…

 

When I build meta-clang, and I set TOOLCHAIN?=”clang” in local.conf it appears to grab llvm-project-source-9.0.1-9.0.1…

 

From: yocto@... <yocto@...> On Behalf Of Anton Antonov
Sent: Tuesday, April 20, 2021 9:51 AM
To: yocto@...
Subject: Re: [yocto] #yocto llvm support

 

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


Hi Steven,

  I used meta-clang in my recipes and I noticed that:
1. The current release of poky uses LLVM v11.1.0 by default (poky/meta/recipes-devtools/llvm/llvm_git.bb)
2. Meta-clang requires LLVM v12.0.0 (meta-clang/conf/layer.conf defines LLVMVERSION = "12.0.0")

As a result just including meta-clang into bblayers.conf will require bitbake to build a new version of LLVM and rebuild everything which uses it

Anton

Monsees, Steven C (US)
 

 

So, does anyone know proper usage here?

 

Is this a fully functional llvm drop under ../poky/meta/recipes-devtools ?

Is it compatible with meta-clang?, and can they be used together to build 3rd party extensions for my platform ?

 

Is it better to add supported components this way rather than building them in directly to EXT SDK ?

 

Also, any known issues with meta-clang under zeus 3.0.4 ?

 

Thanks,

Steve

 

From: Monsees, Steven C (US)
Sent: Tuesday, April 20, 2021 10:01 AM
To: 'Anton Antonov' <anton.antonov@...>; yocto@...
Subject: RE: [yocto] #yocto llvm support

 

 

I noticed similar behavior…

 

I am running zeus 3.0.4, “devtool sdk-install llvm” will get llvm 8.0.1…

 

When I build meta-clang, and I set TOOLCHAIN?=”clang” in local.conf it appears to grab llvm-project-source-9.0.1-9.0.1…

 

From: yocto@... <yocto@...> On Behalf Of Anton Antonov
Sent: Tuesday, April 20, 2021 9:51 AM
To: yocto@...
Subject: Re: [yocto] #yocto llvm support

 

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


Hi Steven,

  I used meta-clang in my recipes and I noticed that:
1. The current release of poky uses LLVM v11.1.0 by default (poky/meta/recipes-devtools/llvm/llvm_git.bb)
2. Meta-clang requires LLVM v12.0.0 (meta-clang/conf/layer.conf defines LLVMVERSION = "12.0.0")

As a result just including meta-clang into bblayers.conf will require bitbake to build a new version of LLVM and rebuild everything which uses it

Anton

Khem Raj
 

On 4/20/21 7:00 AM, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
I noticed similar behavior…
I am running zeus 3.0.4, “devtool sdk-install llvm” will get llvm 8.0.1…
When I build meta-clang, and I set TOOLCHAIN?=”clang” in local.conf it appears to grab llvm-project-source-9.0.1-9.0.1…
this is intentional, when you use meta-clang, then llvm is preferred from LLVM since them we have consistent version of llvm for clang and others.

*From:*yocto@... <yocto@...> *On Behalf Of *Anton Antonov
*Sent:* Tuesday, April 20, 2021 9:51 AM
*To:* yocto@...
*Subject:* Re: [yocto] #yocto llvm support
*_External Email Alert_*
*This email has been sent from an account outside of the BAE Systems network.*
Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.
Hi Steven,
  I used meta-clang in my recipes and I noticed that:
1. The current release of poky uses LLVM v11.1.0 by default (poky/meta/recipes-devtools/llvm/llvm_git.bb)
2. Meta-clang requires LLVM v12.0.0 (meta-clang/conf/layer.conf defines LLVMVERSION = "12.0.0")
As a result just including meta-clang into bblayers.conf will require bitbake to build a new version of LLVM and rebuild everything which uses it
Anton

1 - 5 of 5