From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: My thoughts on the future of OE?
Date: Fri, 02 May 2014 15:23:17 +0100 [thread overview]
Message-ID: <5363AA55.4070305@communistcode.co.uk> (raw)
In-Reply-To: <CAJTo0LaYfVWuBkn4wsHcjWQvoGBv6r+U+Vd+ozb=_=ynPYvkHQ@mail.gmail.com>
On 02/05/14 14:47, Burton, Ross wrote:
> On 2 May 2014 14:00, Mike Looijmans <mike.looijmans@topic.nl> wrote:
>> Just about fifteen minutes ago I was asked the question of "Yay, I could
>> build a complete image for the board from scratch. Now how do I create and
>> run a HelloWorld application on it?"
>
> Depending on context simply adding the "tools-sdk dev-pkgs"
> IMAGE_FEATURES is sufficient to build applications on the target, as
> long as it's for the hello world or iterative development approaches.
> Obviously a recipe would need to be written at some point but getting
> a toolchain in the image for development on the target is trivial.
>
> Ross
>
Or generating and installing the SDK, then develop -> cross compile ->
copy to target -> run -> rinse and repeat.
Then when working, update your applications recipe to point to the new
revision and have a "clean" production image pop out.
The pain points with this come when you want to use new libraries etc
and you have to do a rootfs + sdk rebuild and upgrade but in reality
these are few and far between.
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
next prev parent reply other threads:[~2014-05-02 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 17:02 My thoughts on the future of OE? Richard Purdie
2014-05-01 17:44 ` Stewart, David C
2014-05-02 13:00 ` Mike Looijmans
2014-05-02 13:47 ` Burton, Ross
2014-05-02 14:10 ` Mike Looijmans
2014-05-02 16:05 ` Philip Balister
2014-05-02 14:23 ` Jack Mitchell [this message]
2014-05-02 19:16 ` Koen Kooi
2014-05-02 19:59 ` Richard Purdie
2014-05-02 20:11 ` Martin Jansa
2014-05-05 11:39 ` David Nyström
2014-05-15 9:58 ` Barros Pena, Belen
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=5363AA55.4070305@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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 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.