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