> I've put in a few fixes (mostly, the issue is that the cupcake branch
> in vendor/htc/dream was grossly outdated). the build-for-dream
> instructions should now work for both cupcake and android-1.5.

> Unfortunately the result is still quite far off, and the open-source
> build is currently missing ~100 files that exist in the ADP1. build.
> I'm trying to figure that out.

> JBQ

> On Mon, Apr 27, 2009 at 10:23 AM, Jean-Baptiste Queru <j...@android.com> wrote:
> > Right now I don't think I can recommend any. I'll be focusing my
> > efforts on android-1.5, but at the moment it's not building.

> > JBQ

> > On Mon, Apr 27, 2009 at 10:20 AM, joel <joe...@gmail.com> wrote:

> >> Thanks yes I got that, but since 1.5 is not an option then what other
> >> branch(es) would you recommend to build & deploy on ADP1 today?

> >> On Apr 27, 11:18 am, Jean-Baptiste Queru <j...@android.com> wrote:
> >>> Things are changing very rapidly those days, and we haven't had time
> >>> to work (yet) on setting up the tools to be able to run the "building
> >>> for dream" instructions on 1.5. That's high on my priority list.

> >>> JBQ

> >>> On Mon, Apr 27, 2009 at 8:13 AM, joel <joe...@gmail.com> wrote:

> >>> > JBQ, thanks for the info on the various branches. I think I understand
> >>> > from your summary that the 'cupcake' and 'master' branches are
> >>> > currently the best ones for building for ADP1, with 'cupcake' being
> >>> > stable? And I guess 'android-1.5' doesn't have working build
> >>> > instructions for ADP1? I am focused on what is supported for the ADP1.

> >>> > The proprietary module issue is not a concern for me at this point.

> >>> > Thanks,
> >>> > Joel

> >>> > On Apr 27, 10:33 am, Jean-Baptiste Queru <j...@android.com> wrote:
> >>> >> Yes, the ADP1 situation is currently unfortunate. We've had to pick
> >>> >> priorities, the priority went to open-sourcing code out of Google, as
> >>> >> that's something that only Googlers can do.

> >>> >> The truth is, ADP1 isn't a phone from Google. While Google has some
> >>> >> influence on it (and provides a number of proprietary apps), It's
> >>> >> neither manufactured nor distributed by Google, and that puts limits
> >>> >> on the ways Google can support it (and espcially on how Google can not
> >>> >> redistribute some of the ADP1-specific files).

> >>> >> We've already shared everything that's not proprietary. All the
> >>> >> missing files fall in the "proprietary" category, and that's why we
> >>> >> have to deal with extract_files.sh and the associated ugliness. None
> >>> >> of the issues are technical: getting fired and then sued by both
> >>> >> Google and the owners of the files in question is indeed just one
> >>> >> sharing-effort away.

> >>> >> If we had been able to share those files, we'd have done so back in
> >>> >> December when ADP1 first shipped.

> >>> >> JBQ

> >>> >> On Mon, Apr 27, 2009 at 7:05 AM, Rajesh S <rajeshs...@gmail.com> wrote:

> >>> >> > JBQ, 'building for dream' sequence still happens to produce working
> >>> >> > firmware out of master branch for ADP1.. but that branch is too
> >>> >> > volatile.
> >>> >> > Something for release-1.5 (android-1.5) and updates for subsequent
> >>> >> > releases would be very helpful.

> >>> >> > Without that, a development phone (ADP1 from google) and open source
> >>> >> > ideology gets a mild set back.

> >>> >> > While others porting to other hardware would have to take care of it
> >>> >> > for themselves, google might have to do more justice for 'dream'
> >>> >> > platform.
> >>> >> > JBQ, especially since that is the hardware development platform for
> >>> >> > you all too inside google, I tend to believe that the open source part
> >>> >> > of the sequence is just sharing-effort away and won't cost much of
> >>> >> > development-effort.

> >>> >> > Yes it of course needs to be isolated from proprietary stuff and
> >>> >> > tested to some extent. But .. well.. please provide it soon :)...
> >>> >> > that's the only request.
> >>> >> > Thanks,
> >>> >> > Rajesh.S

> >>> >> > On Apr 27, 2:01 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> >>> >> >> At this point the "building for dream" instructions have fallen a fair
> >>> >> >> bit behind. They used to apply to 1.0, but were semi-maintained
> >>> >> >> halfway between 1.0 and 1.5, and as a result don't really apply to
> >>> >> >> any.

> >>> >> >> Once the 1.5 dust settles, it'll hopefully be possible to put
> >>> >> >> instructions back together that apply to it and produce a working
> >>> >> >> result.

> >>> >> >> JBQ

> >>> >> >> On Mon, Apr 27, 2009 at 1:19 AM, Rajesh S <rajeshs...@gmail.com> wrote:

> >>> >> >> > Thanks a lot JBQ for a very useful explanation.
> >>> >> >> > But one question still lingers. Is any branch other than 'master'
> >>> >> >> > ready for 'dream'?
> >>> >> >> > 'Building for dream' provides a sequence but I fear it won't work with
> >>> >> >> > 1.5 as that might need a newer kernel even on the device.
> >>> >> >> > Master still seems to lag behind 1.5 . Would 1.5 get into master in
> >>> >> >> > near future?

> >>> >> >> > And would we be able to build android-1.5 for producing a dream-
> >>> >> >> > firmware sans the proprietary stuff to match the upcoming release?

> >>> >> >> > Thanks and regards,
> >>> >> >> > Rajesh.S

> >>> >> >> > On Apr 26, 2:29 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> >>> >> >> >> At the moment repo doesn't support tagged manifests, so we had to
> >>> >> >> >> create a branch in the manifest repository to be able to make 1.5
> >>> >> >> >> available with repo -b.

> >>> >> >> >> Here's the current situation:

> >>> >> >> >> -in each "code" repository:
> >>> >> >> >> *release-1.0 is the branch for 1.0 as it was originally released. It
> >>> >> >> >> should be considered read-only (i.e. we don't normally accept
> >>> >> >> >> submissions into it).
> >>> >> >> >> *cdma-import is the branch that was used by Teleca (a member of OHA)
> >>> >> >> >> to work on CDMA support in Android. read-only.
> >>> >> >> >> *cupcake is the branch that follows the cupcake source tree that
> >>> >> >> >> exists inside Google. it's read-only.
> >>> >> >> >> *donut is the branch for the first named project after cupcake.It's
> >>> >> >> >> still in the process of being set up. At the moment it's still
> >>> >> >> >> identical to cupcake. We might accept limited contributions into it at
> >>> >> >> >> some point in the future (as we transition away from the model that we
> >>> >> >> >> used for cupcake).
> >>> >> >> >> *master is the branch for all projects after donut. We accept
> >>> >> >> >> contributions into it.

> >>> >> >> >> *android-1.0 tags the original 1.0 code drop.
> >>> >> >> >> *android-sdk-1.5-pre tags the 1.5 preview SDK. It's the open-source
> >>> >> >> >> part of the exact source that was used to build the SDK, so it can be
> >>> >> >> >> used e.g. to match stack traces.
> >>> >> >> >> *android-1.5 tags the official 1.5 release of the Android Open-Source
> >>> >> >> >> Project. It's the one that should be used by people porting Android
> >>> >> >> >> 1.5 to devices.

> >>> >> >> >> -within the "manifest" repository:
> >>> >> >> >> *there are the same branches as in the "code" repositories, which
> >>> >> >> >> point to the matching branches in all the code repositories.
> >>> >> >> >> *there are branches for android-1.5 and android-sdk-1.5-pre, which
> >>> >> >> >> point to the matching tags in all the code repositories (those have to
> >>> >> >> >> be branches as an artifact of the way repo currently works).

> >>> >> >> >> *there are the same tags as in the "code" repositories.

> >>> >> >> >> In summary, for practical purposes:
> >>> >> >> >> -globally:
> >>> >> >> >> *use repo init -b {release-1.0,cupcake,donut,master} to track the
> >>> >> >> >> state of those projects (though obviously release-1.0 and cupcake
> >>> >> >> >> aren't going to see much more action at this point).
> >>> >> >> >> *use repo init -b {android-sdk-1.5-pre,android-1.5} to get the frozen
> >>> >> >> >> state of those releases.

> >>> >> >> >> -locally in a "code" repository:
> >>> >> >> >> *the korg/{release-1.0,cupcake,donut,master} remotes branches point to
> >>> >> >> >> the matching upstream branches.
> >>> >> >> >> *the {android-sdk-1.5-pre,android-1.5} tags point to those specific releases.

> >>> >> >> >> I hope that makes sense.

> >>> >> >> >> JBQ

> >>> >> >> >> On Sun, Apr 26, 2009 at 1:19 AM, Rajesh S <rajeshs...@gmail.com> wrote:

> >>> >> >> >> > Just downloaded android-1.5 with the "-b" on init. But seemingly it is
> >>> >> >> >> > a tag and not exactly a branch? Is that a tag on a open branch (like
> >>> >> >> >> > master)?

> >>> >> >> >> > On Apr 26, 9:05 am, Rajesh S <rajeshs...@gmail.com> wrote:
> >>> >> >> >> >> Hi,
> >>> >> >> >> >> Now that android-1.5 branch is available on the repo, could somebody
> >>> >> >> >> >> tell us what the branches mean at this stage?

> >>> >> >> >> >> How suitable is android-1.5 branch for the device (dream)?
> >>> >> >> >> >> Like how far is 1.5 merged into master?
> >>> >> >> >> >> What about cupcake and donut?

> >>> >> >> >> >> And could you please ensure a open-source branch almost in sync with
> >>> >> >> >> >> your official release of 1.5 sans the binaries and close sourced
> >>> >> >> >> >> stuff? Something that could compile to the same level as the release
> >>> >> >> >> >> for dream?

> >>> >> >> >> >> Sorry for repeating the last request.

> >>> >> >> >> >> Thanks in advance,
> >>> >> >> >> >> Rajesh.S

> >>> >> >> >> --
> >>> >> >> >> Jean-Baptiste M. "JBQ" Queru
> >>> >> >> >> Android Engineer, 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.

> >>> >> >> --
> >>> >> >> Jean-Baptiste M. "JBQ" Queru
> >>> >> >> Android Engineer, Google.

> ...

> read more »