From: Philip Balister <philip@balister.org>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: What package installs a C compiler on my target?
Date: Wed, 08 Jan 2014 10:17:31 -0500 [thread overview]
Message-ID: <52CD6C0B.9090705@balister.org> (raw)
In-Reply-To: <52CD692A.80504@topic.nl>
On 01/08/2014 10:05 AM, Mike Looijmans wrote:
> On 01/08/2014 02:50 PM, Philip Balister wrote:
>> On 01/08/2014 08:24 AM, Mike Looijmans wrote:
>>> Probably a silly question that has been asked a thousand times, but my
>>> searches on Google only give me the answer to the wrong question (how to
>>> build FOR the target, which I already know how to do).
>>>
>>> I want to run the C compiler on the board itself. That is, a GCC that
>>> runs on the board and compiles (and links etc.) C code for that board.
>>>
>>> What package(s) do I need to build and install to accomplish this?
>>
>> From one of my images:
>>
>>
>> IMAGE_FEATURES += "splash ssh-server-openssh tools-sdk \
>> tools-debug debug-tweaks \
>> dev-pkgs dbg-pkgs \
>> "
>> looks like tools-sdk is the one you want. dev- and dbg- packages might
>> also be helpful, but will make the image larger. Especially the debug
>> ones.
>
> $ bitbake tools-sdk
> ERROR: Nothing PROVIDES 'tools-sdk'
>
> So I guess it's a package that's provided in another layer (I have
> oe-core and most of meta-oe).
The complete recipe is here:
https://github.com/balister/meta-sdr/blob/master/recipes-images/images/gnuradio-dev-image.bb
Note the inherit core-image at the bottom.
Philip
>
> So far, the following set I've derived through trial and error seems to
> come close:
>
> TARGET_COMPILER_TOOLS = "\
> binutils \
> binutils-symlinks \
> cpp \
> cpp-symlinks \
> g++ \
> g++-symlinks \
> gcc \
> gcc-symlinks \
> make \
> packagegroup-core-standalone-sdk-target \
> "
>
> This allows a basic "hello world" to compile on target in C and C++
> code. Make wasn't really required, but it's very convenient to have...
>
> I'm mostly surprised that there wasn't a packagegroup to contain this set.
>
> It increased the image size to about 130MB, but in this particular case,
> that won't be a problem.
>
> Anyway, thanks for the tips all. Guess this list may be useful to others...
>
> Mike.
>
>
> Met vriendelijke groet / kind regards,
>
> Mike Looijmans
>
> TOPIC Embedded Systems
> Eindhovenseweg 32-C, NL-5683 KH Best
> Postbus 440, NL-5680 AK Best
> Telefoon: (+31) – (0)499 - 33.69.79
> Telefax: (+31) - (0)499 - 33.69.70
> E-mail: mike.looijmans@topic.nl
> Website: www.topic.nl
>
> Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn
> uitsluitend bestemd voor de geadresseerde, zoals die blijkt uit het
> e-mail bericht en/of de bijlagen. Er kunnen gegevens met betrekking tot
> een derde instaan. Indien u als niet-geadresseerde dit bericht en de
> bijlagen ontvangt, terwijl u niet bevoegd of gemachtigd bent om dit
> bericht namens de geadresseerde te ontvangen, wordt u verzocht de
> afzender hierover direct te informeren en het e-mail bericht met de
> bijlagen te vernietigen. Ieder gebruik van de inhoud van het e-mail
> bericht, waaronder de daarbij behorende bijlagen, door een ander dan de
> geadresseerde is onrechtmatig jegens ons dan wel de eventueel in het
> e-mail bericht of de bijlagen voorkomende andere personen. TOPIC
> Embedded Systems is niet aansprakelijk voor enigerlei schade
> voortvloeiend uit het gebruik en/of acceptatie van dit e-mail bericht of
> de daarbij behorende bijlagen.
>
> The contents of this message, as well as any enclosures, are addressed
> personally to, and thus solely intended for the addressee. They may
> contain information regarding a third party. A recipient who is neither
> the addressee, nor empowered to receive this message on behalf of the
> addressee, is kindly requested to immediately inform the sender of
> receipt, and to destroy the message and the enclosures. Any use of the
> contents of this message and/or the enclosures by any other person than
> the addressee or person who is empowered to receive this message, is
> illegal towards the sender and/or the aforementioned third party. TOPIC
> Embedded Systems is not liable for any damage as a result of the use
> and/or acceptance of this message and as well as any enclosures.
>
>
next prev parent reply other threads:[~2014-01-08 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 13:08 [PATCH 0/2] Package upgrades Irina Patru
2014-01-08 13:08 ` [PATCH 1/2] libtasn1: upgrade to 3.4 Irina Patru
2014-01-08 13:08 ` [PATCH 2/2] libsoup-2.4: upgrade to 2.45.3 Irina Patru
2014-01-08 13:24 ` What package installs a C compiler on my target? Mike Looijmans
2014-01-08 13:48 ` Phil Blundell
2014-01-08 14:57 ` Mike Looijmans
2014-01-08 13:50 ` Philip Balister
2014-01-08 15:05 ` Mike Looijmans
2014-01-08 15:14 ` Burton, Ross
2014-01-08 15:17 ` Richard Purdie
2014-01-08 15:17 ` Philip Balister [this message]
2014-01-08 15:21 ` Stanacar, StefanX
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=52CD6C0B.9090705@balister.org \
--to=philip@balister.org \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@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