From: Liviu Gheorghisan <liviu.gheorghisan@enea.com>
To: Jim Rafert <jimr@spectralogic.com>,
"Yu, Chan KitX" <chan.kitx.yu@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Building clang with Yocto
Date: Tue, 9 Dec 2014 18:54:50 +0200 [thread overview]
Message-ID: <5487295A.6030403@enea.com> (raw)
In-Reply-To: <86196249137E0843B2E0673D4F731E0C0108E2919B@reactor.sldomain.com>
[-- Attachment #1: Type: text/plain, Size: 4575 bytes --]
Hello Jim,
You must add your override of do_install_class-nativesdk() in the recipe
that builds clang/llvm that will not affect how gcc gets installed in
the SDK.
You can have as many do_install_class-nativesdk() overrides across
various recipes as you like, without them conflicting. Basically this is
how every tool from the SDK gets installed there.
- Liviu
On 12/09/2014 06:47 PM, Jim Rafert wrote:
> Hi Liviu,
>
> Thanks for the tip. I had everything but the override for
> do_install_class-nativesdk().
>
> One question please.
>
> Will that override prevent the gcc compilers from being installed in
> nativesdk? Or should I duplicate the existing
> do_install_class-nativesdk(), and add the clang stuff?
>
> -Jim-
>
>
> ------------------------------------------------------------------------
> *From:* Liviu Gheorghisan [liviu.gheorghisan@enea.com]
> *Sent:* Tuesday, December 09, 2014 9:27 AM
> *To:* Yu, Chan KitX; Jim Rafert; yocto@yoctoproject.org
> *Subject:* Re: [yocto] Building clang with Yocto
>
> Hello Yu, Jim
>
> I think you can get the clang executable into the SDK installer script
> with something like this:
>
> 1. Add this dependency in nativesdk-packagegroup-sdk-host.bb:
> *RDEPENDS_${PN} += "nativesdk-<name-of-clang-recipe>"*
>
> 2. In the clang recipe add this install() overwrite for the nativesdk
> class - this will install it into the SDK sysroot:
> *do_install_class-nativesdk() {
> install -d ${D}${bindir}
> install -m 0755 clang ${D}${bindir}
> }*
>
> 3. The clang recipe (I don't know if it has a recipe of its own, or
> it's part of the LLVM recipe) should also inherit from nativesdk:
> *BBCLASSEXTEND = "nativesdk"*
>
> Basically this should get your clang executable inside the SDK
> installer. Sure you can add more executables related to clang (like
> the llvm-related ones) in the install_class-nativesdk() function.
>
> - Liviu Gheorghisan
>
> On 12/09/2014 04:36 AM, Yu, Chan KitX wrote:
>> I **think** I'm just inches away from success. I think I just need to invoke a correct install command somewhere in the do_install function but so far I have not managed to do so. But right now the alternative way of jamming the compiler into the SDK sounds tempting to me.
>>
>> -----Original Message-----
>> From: Yu, Chan KitX
>> Sent: Tuesday, December 09, 2014 9:19 AM
>> To: 'Jim Rafert';yocto@yoctoproject.org
>> Subject: RE: Building clang with Yocto
>>
>> Hi Jim,
>>
>> How did you jam the clang compiler into the SDK tarball?
>>
>> Chan Kit
>>
>> -----Original Message-----
>> From: Jim Rafert [mailto:jimr@spectralogic.com]
>> Sent: Tuesday, December 09, 2014 1:48 AM
>> To:yocto@yoctoproject.org; Yu, Chan KitX
>> Subject: Building clang with Yocto
>>
>> Hello Chan,
>>
>> I have been working to a similar goal, to include clang in the toolchain to be used for compiling applications to run on the target. Using clang to compile the OS and kernel are not required or desired by me.
>>
>> You may get some insight from the thread I started in November on the subject. I'm not sure that this contains all of the posts on the subject. You may want to search the archive for November.
>>
>> I have not been successful yet in getting clang actually packaged in the toolchain, in the Yocto build, but at least it builds. I have a postbuild script that takes the built clang compiler from the work directory and jams it into the SDK tarball that is embedded in the sdk install script.
>>
>> -Jim-
>>
>>
>> ________________________________________
>> From:yocto-bounces@yoctoproject.org [yocto-bounces@yoctoproject.org] on behalf ofyocto-request@yoctoproject.org [yocto-request@yoctoproject.org]
>> Sent: Monday, December 08, 2014 2:56 AM
>> To:yocto@yoctoproject.org
>> Subject: yocto Digest, Vol 51, Issue 26
>>
>> Send yocto mailing list submissions to
>> yocto@yoctoproject.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.yoctoproject.org/listinfo/yocto
>> or, via email, send a message with subject or body 'help' to
>> yocto-request@yoctoproject.org
>>
>> You can reach the person managing the list at
>> yocto-owner@yoctoproject.org
>>
>> When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..."
>
--
Liviu Gheorghisan
Software Engineer
Enea Romania
Splaiul Independentei 319, OB403A,
District 6, Bucharest,
Romania, 060044
http://www.enea.com
[-- Attachment #2: Type: text/html, Size: 8173 bytes --]
next prev parent reply other threads:[~2014-12-09 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 17:48 Building clang with Yocto Jim Rafert
2014-12-09 1:19 ` Yu, Chan KitX
2014-12-09 16:06 ` Jim Rafert
2014-12-09 2:36 ` Yu, Chan KitX
2014-12-09 16:27 ` Liviu Gheorghisan
2014-12-09 16:47 ` Jim Rafert
2014-12-09 16:54 ` Liviu Gheorghisan [this message]
2014-12-10 3:24 ` Yu, Chan KitX
2014-12-22 3:33 ` Yu, Chan KitX
2014-12-22 11:21 ` Paul Eggleton
2014-12-23 8:21 ` Yu, Chan KitX
2014-12-23 16:57 ` Jim Rafert
2014-12-24 5:54 ` Yu, Chan KitX
2014-12-22 17:02 ` Jim Rafert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5487295A.6030403@enea.com \
--to=liviu.gheorghisan@enea.com \
--cc=chan.kitx.yu@intel.com \
--cc=jimr@spectralogic.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.