All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Mike Looijmans <mike.looijmans@topic.nl>,
	 "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: My thoughts on the future of OE?
Date: Fri, 02 May 2014 09:05:04 -0700	[thread overview]
Message-ID: <5363C230.5070508@balister.org> (raw)
In-Reply-To: <5363A741.6080508@topic.nl>

On 05/02/2014 07:10 AM, Mike Looijmans wrote:
> On 05/02/2014 03:47 PM, 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
>>
> 
> That would be for "how do I create and run a HelloWorld application on
> target without using my PC at all?".
> 
> I guess I'm still a bit stuck in the era where the target had very
> limited resources. For first time users, this is much easier, and for a
> workshop, I've indeed supplied a dozen boards that had editors,
> compilers and library headers pre-installed for immediate development.
> 
> That will work for hello-world style apps, but for more complex projects
> that draw in a few dozen complex libraries (gstreamer comes to mind)
> this is not going to be very satisfactory.
> 
> 
> What he was asking for was "How do I use the cross-compile environment
> to develop my own application and run it on the target machine?"
> 
> 

https://github.com/balister/meta-sdr/wiki/CrossCompile

IS what I tell people for GNU Radio. The generic method should be OK for
other cases. I need to collect techniques to move output onto the target.

Philip


  reply	other threads:[~2014-05-02 16:11 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 [this message]
2014-05-02 14:23     ` Jack Mitchell
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=5363C230.5070508@balister.org \
    --to=philip@balister.org \
    --cc=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.