On Wed, 2014-01-08 at 16:05 +0100, 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).
No, tools-sdk it's not a bitbake target/package, it's an image feature
that you need to add it to your image, e.g in local.conf:
IMAGE_FEATURES_append = " tools-sdk"
You'll probably want to add dev-pkgs too (that will install the devel
packages/headers)
The glory details are in core-image.bbclass, basically tools-sdk
installs packagegroup-core-sdk and
packagegroup-core-standalone-sdk-target. These are actually targets that
you can build. If you want to see exactly on which packages these groups
depend on you can have a look at
meta/recipes-core/packagegroups/packagegroup-core*sdk*.bb recipes.
Cheers,
Stefan
>
> 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.looijm...@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.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
