Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Initial work on an Android SDK via openembedded
Date: Sat, 10 Apr 2010 15:01:16 +0200	[thread overview]
Message-ID: <1270904476.2579.0.camel@gnutoo-desktop> (raw)
In-Reply-To: <n2ue96fffc41004082246g4269c2d2nd6aa9f3e7260db27@mail.gmail.com>

On Fri, 2010-04-09 at 15:46 +1000, Angus Lees wrote:
> Just an FYI:
> 
> I put together an alternative Android NDK using Openembedded:
>  git://github.com/anguslees/openembedded-android.git
> 
> It currently uses the prebuilt Android libc (bionic) and various tools
> from the Google Android NDK/SDK, but builds gcc, etc from Openembedded
> source.  I expect to expand it to build the other pieces from source
> eventually.  I had to patch the gcc and other recipies a little, which
> is why it's a git branch rather than a self-contained bitbake
> collection.
> 
> This is my first-ever look at bitbake or openembedded, so apologies if
> any of the recipies are atrocious ;)
> 
> (Totally unsupported by Google.  I work for Google but don't work on
> anything to do with Android - I just happen to have an Android handset
> and a desire to write native apps for it in my free time)
> 
WOW!!! great!!!

Denis.





  parent reply	other threads:[~2010-04-10 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  5:46 Initial work on an Android SDK via openembedded Angus Lees
2010-04-09 10:32 ` Michael 'Mickey' Lauer
2010-04-10 13:01 ` GNUtoo [this message]
2010-04-15 17:56   ` Patchwork Konrad Mattheis
2010-04-15 18:59     ` Patchwork Philip Balister

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=1270904476.2579.0.camel@gnutoo-desktop \
    --to=gnutoo@no-log.org \
    --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