We're approaching from two fronts:
-we're moving to using true product definitions for everything (no
more LOCAL_MODULE_TAGS := user), so that it'll be possible to
explicitly control exactly what ends up in the result without having
to disable individual makefiles (which is what BUILD_TINY_ANDROID
did).
-we're tweaking the build system so that by default it only compiles
what gets installed. That way, if you have a product definition that
only has the same low-level components that you'd expect in
TINY_ANDROID, you won't be unnecessarily compiling the entire world.
I'm not sure which of those are in AOSP at the moment.
JBQ
On Mon, Jan 7, 2013 at 12:24 PM, Ehtesh Choudhury
<
merloc...@gmail.com> wrote:
> I would also like to know if there any alternatives to BUILD_TINY_ANDROID.
>
>
> On Saturday, December 29, 2012 12:39:48 PM UTC-5, trevd wrote:
>>
>> Hi
>>
>> I see the BUILD_TINY_ANDROID option has now been removed from the AOSP
>> Master Branch Build System,
>>
>> Is there any alternative options to achieve a similar minimal build?
>>
>> Thanks
>
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to
android-...@googlegroups.com
> To unsubscribe from this group, send email to
>
android-buildi...@googlegroups.com
> For more options, visit this group at
>
http://groups.google.com/group/android-building?hl=en
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.