I strongly recommend syncing new clients: our implementation of git
and repo can deal with those better, so you're likely to sync a new
client faster than an incremental one.
The branches that you care about:
-android-4.0.1_r1 is the release branch, ITL41D, that is expected to
ship on Galaxy Nexus. That's the one you want to be using to port to
devices.
-ics-mr0 is the ICS development branch. It contains a few changes that
aren't in the release branch, so it might not be as stable. That's the
one you want to use if you plan to contribute to CTS.
-master is the usual master branch, it contains all of ics-mr0 plus a
few extra changes. That's the branch that you should use if you want
to contribute to the platform.
A few notes:
-All the external contributions that had been accepted in AOSP before
the servers went down have been merged into ICS.
-The release and development branch require the "classic" host
configurations (Ubuntu 10.04, or MacOS 10.6 with XCode 3). The master
branch had a few tweaks to make it work better on newer systems
(Ubuntu 11.10, Mac OS 10.7 with XCode 4.2) but it's not 100% there
yet.
-In addition to the usual emulator targets and Galaxy Nexus (a.k.a.
maguro), the master branch works experimentally on PandaBoard too
(a.k.a. panda).
-Proprietary binaries for 4.0.1 will be available in the next few
hours from their usual location
http://code.google.com/android/nexus/drivers.html
JBQ
--
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
warning.
I'm seeing this error - am I being stupid (again) or is something missing?
fatal: '../platform/abi/cpp.git' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
error: Cannot fetch platform/abi/cpp
--
Dominic Binks: dbi...@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
From there, in a clean directory, you should be able to sync a new client.
JBQ
> --
> 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
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
Beyond that, though, Nexus One is considered obsolete for the purpose
of AOSP, but I wouldn't be surprised to see some creatively
enterprising community members find a way to make things somewhat
work.
JBQ
> --
> 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
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
JBQ
> --
> 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
>
--
JBQ
Syncing refers to downloading ICS source code. If you have an
unsupported (non-nexus) phone, you may not be able to build the source
code to run on your device.
ok thnx so much that helps much thank u
I don't have any deeper insight in the exact changes in the graphics
pipeline since Gingerbread, sorry.
JBQ
Sorry, but we can really only provide support for nexus devices.
Thanks,
JBQ
We had to make a choice: release ITL41D in its Galaxy-Nexus-only
state, or wait until we have a build that also works on Nexus S. There
are pros and cons to either approach, and we picked the former.
JBQ
If that's an older previous repo that hasn't been synced in months. It
is theoretically possible to update an existing client to use the new
repo. In .repo/repo/.git/config, under remote "origin", change the url
to be https://android.googlesource.com/tools/repo
JBQ
JBQ
On Tue, Nov 15, 2011 at 3:55 AM, Matt Oakes <oak...@googlemail.com> wrote:
> Does this mean we will be getting support for crespo in ASOP ICS in the
> future?
>
JBQ
Perfect. That's great :-) just good to know it will be out at some point in the future. We have some nexus s devices we currently use for testing and it would be a shame to not be able to use them.
Is there any estimates on how long before it will be out?
Great work! Loving that it's out before the device :-)
JBQ
It seems mines fairly good. I predicted that would be the answer ;-)
> I followed above suggestions, but still get the error:
>
> repo sync
> fatal: '../platform/abi/cpp.git' does not appear to be a git
> repository
> fatal: The remote end hung up unexpectedly
> error: Cannot fetch platform/abi/cpp
Then you're *still* using an old Repo. Start off with an empty directory
when you run "repo init", and make sure your Repo really is the latest
one. The hostname in the URL in the repo script should be
android.googlesource.com rather than android.git.kernel.org (although,
if that was the problem you wouldn't get this far in the first place).
--
Magnus B�ck Opinions are my own and do not necessarily
SW Configuration Manager represent the ones of my employer, etc.
Sony Ericsson
On Tue, Nov 15, 2011 at 3:16 PM, Magnus Bäck
<magnu...@sonyericsson.com> wrote:
> On Tuesday, November 15, 2011 at 21:04 CET,
> powder <jonas....@gmail.com> wrote:
>
>> I followed above suggestions, but still get the error:
>>
>> repo sync
>> fatal: '../platform/abi/cpp.git' does not appear to be a git
>> repository
>> fatal: The remote end hung up unexpectedly
>> error: Cannot fetch platform/abi/cpp
>
> Then you're *still* using an old Repo. Start off with an empty directory
> when you run "repo init", and make sure your Repo really is the latest
> one. The hostname in the URL in the repo script should be
> android.googlesource.com rather than android.git.kernel.org (although,
> if that was the problem you wouldn't get this far in the first place).
>
> --
> Magnus Bäck Opinions are my own and do not necessarily
> SW Configuration Manager represent the ones of my employer, etc.
> Sony Ericsson
>
> --
> 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