Hey everyone!
I've had some questions about what "TINY_ANDROID" is (and isn't).
I put together this Wiki to answer any questions and make some recommendations for its use.
https://wiki.linaro.org/Platform/Android/UseTinyAndroid
Basically this build can be built from source in about 20 min (kernel included) and support most of the low level userspace tools we need to work with. It should be ideal for 64-bit native Android porting.
On Wed, Aug 22, 2012 at 4:35 AM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Hey everyone!
I've had some questions about what "TINY_ANDROID" is (and isn't).
I put together this Wiki to answer any questions and make some recommendations for its use.
That's good info. So Tiny Android does not even include dalvik? nice ...
I guess there is no minimal manifest maintained by google with just the bits needed for TINY?
Maybe I should set the tracking snowball to tiny for a while since it will take a while before there is frame buffer support.
Do I only have to add BUILD_TINY_ANDROID=true in the build configuration or is there something more that needs to be done?
/Patrik
On 22 August 2012 11:21, Alexander Sack asac@linaro.org wrote:
On Wed, Aug 22, 2012 at 4:35 AM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Hey everyone!
I've had some questions about what "TINY_ANDROID" is (and isn't).
I put together this Wiki to answer any questions and make some recommendations for its use.
That's good info. So Tiny Android does not even include dalvik? nice ...
I guess there is no minimal manifest maintained by google with just the bits needed for TINY?
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
On 22 August 2012 12:51, Patrik Ryd patrik.ryd@linaro.org wrote:
Maybe I should set the tracking snowball to tiny for a while since it will take a while before there is frame buffer support.
Do I only have to add BUILD_TINY_ANDROID=true in the build configuration or is there something more that needs to be done?
Just make sure you use the linaro_android_4.1.1 branches of everything - AOSP branches don't know how to include a kernel in the build process (and what extra tools need to be compiled to do that).
ttyl bero
On 22 August 2012 11:21, Alexander Sack asac@linaro.org wrote:
I guess there is no minimal manifest maintained by google with just the bits needed for TINY?
No, but that's easy to build -- stuff actually used by TINY:
build bionic system/core system/extras/ext4_utils system/extras/su external/gcc-demangle external/mksh external/yaffs2 external/zlib prebuilt/tools/gcc-sdk
ttyl bero
On Wed, Aug 22, 2012 at 1:21 PM, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
On 22 August 2012 11:21, Alexander Sack asac@linaro.org wrote:
I guess there is no minimal manifest maintained by google with just the bits needed for TINY?
No, but that's easy to build -- stuff actually used by TINY:
build bionic system/core
everything in core? or just a subset of: http://android.git.linaro.org/gitweb?p=platform/system/core.git%3Ba=tree%3Bh...
system/extras/ext4_utils system/extras/su external/gcc-demangle external/mksh
external/yaffs2
is yaffs2 used for our GN build?
external/zlib prebuilt/tools/gcc-sdk
thanks.
On 22 August 2012 13:25, Alexander Sack asac@linaro.org wrote:
On Wed, Aug 22, 2012 at 1:21 PM, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
No, but that's easy to build -- stuff actually used by TINY: system/core
everything in core? or just a subset of: http://android.git.linaro.org/gitweb?p=platform/system/core.git%3Ba=tree%3Bh...
A subset - the build process excludes charger, libpixelflinger, libsysutils and netcfg if BUILD_TINY_ANDROID == true. But of course when it comes down to writing a manifest, that's irrelevant because manifests don't work at subtree levels
external/yaffs2
is yaffs2 used for our GN build?
AFAIK it's only needed to build boot.img when making droid or droidcore instead of *tarball, so chances are we can omit it
ttyl bero
On 22 August 2012 07:56, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
On 22 August 2012 13:25, Alexander Sack asac@linaro.org wrote:
On Wed, Aug 22, 2012 at 1:21 PM, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
No, but that's easy to build -- stuff actually used by TINY: system/core
everything in core? or just a subset of: http://android.git.linaro.org/gitweb?p=platform/system/core.git%3Ba=tree%3Bh...
A subset - the build process excludes charger, libpixelflinger, libsysutils and netcfg if BUILD_TINY_ANDROID == true. But of course when it comes down to writing a manifest, that's irrelevant because manifests don't work at subtree levels
external/yaffs2
is yaffs2 used for our GN build?
AFAIK it's only needed to build boot.img when making droid or droidcore instead of *tarball, so chances are we can omit it
ttyl bero
So I spent about an hour working with a stripped down TINY_ANDROID manifest.
I don't think its going to be worth it. Its not supported and there's a whole bunch of little dependencies here and there that I'm sure will change with each new Android release. We'll just have people check out the whole thing.
Same problem with dvk, the little project to build dalvik stand alone. Nice idea but a PITA to maintain.
Regards, Tom
On Aug 22, 2012, at 3:18 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 22 August 2012 07:56, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
On 22 August 2012 13:25, Alexander Sack asac@linaro.org wrote:
On Wed, Aug 22, 2012 at 1:21 PM, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
No, but that's easy to build -- stuff actually used by TINY: system/core
everything in core? or just a subset of: http://android.git.linaro.org/gitweb?p=platform/system/core.git%3Ba=tree%3Bh...
A subset - the build process excludes charger, libpixelflinger, libsysutils and netcfg if BUILD_TINY_ANDROID == true. But of course when it comes down to writing a manifest, that's irrelevant because manifests don't work at subtree levels
external/yaffs2
is yaffs2 used for our GN build?
AFAIK it's only needed to build boot.img when making droid or droidcore instead of *tarball, so chances are we can omit it
ttyl bero
So I spent about an hour working with a stripped down TINY_ANDROID manifest.
I don't think its going to be worth it. Its not supported and there's a whole bunch of little dependencies here and there that I'm sure will change with each new Android release. We'll just have people check out the whole thing.
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-android@lists.linaro.org
-
Alexander Sack -
Bernhard Rosenkränzer -
Patrik Ryd -
Tom Gall -
Zach Pfeffer