|| ||Jean-Baptiste Queru <jbq-z5hGa2qSFaRBDgjK7y7TUQ-AT-public.gmane.org> |
|| ||android-platform-/JYPxA39Uh5TLH3MbocFFw-AT-public.gmane.org |
|| ||Building AOSP: let's call this "1.0" |
|| ||Mon, 5 Oct 2009 14:42:47 -0700|
|| ||Article, Thread
I've been doing some additional work to put together a
maintainable/scalable build configuration structure for AOSP.
Here's the current status:
-there's a product "aosp_us" which builds for the emulator.
-there's a product "aosp_dream_us", which builds for dream (i.e. ADP1).
-I've added a few entries in the lunch menu to get quick access to those.
-the old "aosp_dream" product is gone.
-aosp-dream-us_userdebug is pretty close to the ADP1 config.
-the aosp configs don't have any of the Google apps (still some
details to be worked out).
-because opencore is different between master and donut, there could
be dragons there when running on dream.
-Calendar is still broken in the exact same way. I haven't had time to
look at this yet.
-as you might have guessed, the point of having *_us configurations is
to also create some *_eu ones. Coming soon.
-this is still master-only at the moment, though I'm planning to
replicate it to donut when the activity quiets down a bit.
I'd like to call this state "1.0 of AOSP". It's not perfect yet, but I
believe that this should allow contributors to test their changes in
better conditions before uploading them for review.
Jean-Baptiste M. "JBQ" Queru
Software Engineer, 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
You received this message because you are subscribed to the Google Groups "android-platform"
To post to this group, send email to android-platform-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en
to post comments)