Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: How to build g++ to run on target?
Date: Wed, 24 Feb 2010 08:57:09 +0000	[thread overview]
Message-ID: <4B84E9E5.8060903@ge.com> (raw)
In-Reply-To: <1266973598.18176.366.camel@trini-m4400>

Tom Rini wrote:
> On Tue, 2010-02-23 at 16:53 -0800, Philip Balister wrote:
>   
>> On 02/23/2010 03:09 PM, Khem Raj wrote:
>>     
>>> On Tue, Feb 23, 2010 at 2:37 PM, Philip Balister<philip@balister.org>  wrote:
>>>       
>>>> On 02/23/2010 05:51 AM, Jay Snyder wrote:
>>>>         
>>>>> I was able to build gcc for installation directly onto the OE target
>>>>> with "bitbake gcc". "bitbake g++" gives me "nothing provides g++".
>>>>>
>>>>> What is the magic bitbake command to provide this?
>>>>>           
>>>> bitbake task-sdk-native, and install task-native-sdk. Anyone know why the
>>>> task creates a package with different name?
>>>>         
>>> may be because
>>>
>>> task-sdk-native.bb:RPROVIDES_${PN} = "task-native-sdk"
>>>       
>> I know that :) I am curious why the renaming.
>>     
>
> And if perhaps we couldn't get a different name altogether?  'native'
> has a meaning normally that's not what it means here.
> task-on-device-sdk is a bit wordy, but avoids 'native'.  Of course,
> 'native development' also has a meaning too.. RPROVIDES perhaps?  Or is
> that just the worst of both worlds.
"target"?

-- 
Martyn Welch (Principal Software Engineer)   |   Registered in England and
GE Intelligent Platforms                     |   Wales (3828642) at 100
T +44(0)127322748                            |   Barbirolli Square, Manchester,
E martyn.welch@ge.com                        |   M2 3AB  VAT:GB 927559189




      parent reply	other threads:[~2010-02-24 13:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1266922802.8892.openembedded-devel@lists.openembedded.org>
2010-02-23 13:45 ` Openembedded-devel Digest, Vol 43, Issue 99 Jay Snyder
2010-02-23 15:25   ` Holger Hans Peter Freyther
2010-02-23 13:51 ` How to build g++ to run on target? Jay Snyder
2010-02-23 18:12   ` Khem Raj
2010-02-23 22:37   ` Philip Balister
2010-02-23 23:09     ` Khem Raj
2010-02-24  0:53       ` Philip Balister
2010-02-24  1:06         ` Tom Rini
2010-02-24  2:33           ` Khem Raj
2010-02-24  3:08             ` Denys Dmytriyenko
2010-02-24  4:01               ` Khem Raj
2010-02-24  8:57           ` Martyn Welch [this message]

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=4B84E9E5.8060903@ge.com \
    --to=martyn.welch@ge.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox