ICS in AOSP: we're live, feel free to sync

Affichage de 142 messages sur 42
ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 14/11/11 15:19
You can go ahead and sync ICS from AOSP.

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.

Re: [android-building] ICS in AOSP: we're live, feel free to sync Dominic Binks 14/11/11 15:22
Hi JBQ,

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

Re: [android-building] ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 14/11/11 15:27
You need a recent version of repo, 1.7.7 or newer, to be able to parse
the new AOSP manifests.

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


>

--
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.

Re: [android-building] ICS in AOSP: we're live, feel free to sync Manish 14/11/11 15:26
I am seeing following error
Initializing project platform/abi/cpp ...

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




--
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



--
Manish Shakya
http://www.manishshakya.com.np
http://secs.oakland.edu/~ganesan/iMX/
Re: ICS in AOSP: we're live, feel free to sync Sandeep 14/11/11 16:14
I have repo version v1.7.7.6, but I keep getting the following error.

Running on Ubuntu 11.04

Exception in thread Thread-8:
Traceback (most recent call last):
  File "/usr/lib/python2.6/threading.py", line 532, in
__bootstrap_inner
    self.run()
  File "/usr/lib/python2.6/threading.py", line 484, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/data/ssp/ics-aosp/.repo/repo/subcmds/sync.py", line 182, in
_FetchHelper
    success = project.Sync_NetworkHalf(quiet=opt.quiet)
  File "/data/ssp/ics-aosp/.repo/repo/project.py", line 926, in
Sync_NetworkHalf
    if alt_dir is None and self._ApplyCloneBundle(initial=is_new,
quiet=quiet):
  File "/data/ssp/ics-aosp/.repo/repo/project.py", line 1444, in
_ApplyCloneBundle
    exist_dst = self._FetchBundle(bundle_url, bundle_tmp, bundle_dst,
quiet)
  File "/data/ssp/ics-aosp/.repo/repo/project.py", line 1506, in
_FetchBundle
    raise DownloadError('HTTP %s%s' % (e.code, msg))
DownloadError: HTTP 403 (Forbidden: Request forbidden -- authorization
will not help)
> >>http://code.google.com/**android/nexus/drivers.html<http://code.google.com/android/nexus/drivers.html>
>
> >> JBQ
>
> > --
> > Dominic Binks: dbi...@codeaurora.org
> > Employee of Qualcomm Innovation Center, Inc.
> > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > --
> > 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<android-...@googlegroups.com>
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@**googlegroups.com<android-building%2Bunsubscr i...@googlegroups.com>
> > For more options, visit this group at
> >http://groups.google.com/**group/android-building?hl=en<http://groups.google.com/group/android-building?hl=en>
>
> --
> Manish Shakyahttp://www.manishshakya.com.nphttp://secs.oakland.edu/~ganesan/iMX/
Re: ICS in AOSP: we're live, feel free to sync Paul Little 14/11/11 16:23
Ok, dumb question. I'm no developer but a N1 owner since the beginning. Is there going to be any way for me to get ICS on my N1 without rooting? It makes sense to me that I'd no longer get OTA updates but I've been downloading builds way before they are released to the public so that's no big deal for me. And I apologize in advance if this is not the right place to ask such a question. Any advice would be awesome. I've been waiting for this since the press event. 

Thanks!
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 14/11/11 16:38
The Nexus One comes with an unlockable bootloader, so there's no need
to play with security holes to install a custom OS on it.

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
>

--
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.

Re: ICS in AOSP: we're live, feel free to sync Kenneth Crudup 14/11/11 16:41
On Nov 14, 4:14 pm, Sandeep <psandee...@gmail.com> wrote:

> I have repo version v1.7.7.6, but I keep getting the following error.
...
> raise DownloadError('HTTP %s%s' % (e.code, msg)) DownloadError: HTTP 403 (Forbidden: Request forbidden -- authorization will not help)

I think the overwhelming demand killed the servers (either that, or
someone's changed their minds about us having it :) ); my ongoing
"repo sync" stopped in its tracks, and my other machine can't even get
off the ground.
Re: ICS in AOSP: we're live, feel free to sync morrildl 14/11/11 16:56
The servers are fine, actually. We know what is causing this, we're
looking into it. Sit tight for a bit.
Re: [android-building] ICS in AOSP: we're live, feel free to sync Karim Yaghmour 14/11/11 16:56

EXCELLENT!!! Thanks so much ... sync in progress :D

--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour

Re: ICS in AOSP: we're live, feel free to sync David Wang 14/11/11 17:17

Are the proprietary graphics binaries needed to support hardware
acceleration?

Meaning if I wanted to get this to run on my Nexus S, would I need the
nexus S 4.0 graphics binaries in order to get the hardware
acceleration features of ICS?
Re: [android-building] ICS in AOSP: we're live, feel free to sync Moontain 14/11/11 17:33
Hi JBQ,

Thanks. The repo sync is in progress.

When the drivers for Nexus S will be updated to ICS at http://code.google.com/android/nexus/drivers.html ? Thanks.

Regards,
Moontain

2011/11/15 Jean-Baptiste Queru <j...@android.com>

--
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

Re: ICS in AOSP: we're live, feel free to sync einmus 14/11/11 17:49
Me too.
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 14/11/11 17:51
I don't expect that you'll be able to easily run ICS with the GB
graphics drivers for Nexus S, and if you get the basic system running
you'll probably run into some "interesting" performance issues.

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
>

--
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.

Re: [android-building] ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 14/11/11 17:52
The files that get released there match consumer releases quite
closely, and we don't have such a release for Nexus S at the moment.

JBQ

Re: ICS in AOSP: we're live, feel free to sync TheMrRoxtar 14/11/11 18:02
god i shouldnt even be asking this but i am new to this a bit. i have
a galaxy s 2 and wanted to know if i sync this will.i get ics. i want
to know what this is for and have a need to learn from you guys.
please help thmx so much.

On Nov 14, 7:52 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> The files that get released there match consumer releases quite
> closely, and we don't have such a release for Nexus S at the moment.
>
> JBQ
>
>
>
>
>
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Conley Owens 14/11/11 18:09
On Mon, Nov 14, 2011 at 6:02 PM, TheMrRoxtar <cddy...@gmail.com> wrote:
> god i shouldnt even be asking this but i am new to this a bit. i have
> a galaxy s 2 and wanted to know if i sync this will.i get ics. i want
> to know what this is for and have a need to learn from you guys.
> please help thmx so much.

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.

Re: ICS in AOSP: we're live, feel free to sync Kenneth Crudup 14/11/11 18:03
On Nov 14, 4:56 pm, morrildl <morri...@google.com> wrote:

> The servers are fine, actually. We know what is causing this, we're looking into it. Sit tight for a bit.

Will you let us know when? So far, I'm still "403"ing.
Re: ICS in AOSP: we're live, feel free to sync blunden 14/11/11 18:10
Any reason the Galaxy Nexus GPU drivers wouldn't work for the Nexus S?
It is the same GPU after all, albeit with a much lower clock speed and
I assume that doesn't get set by the GPU driver.

Also, is there any documentation for the changes you implemented in
ICS compared to GB for the GPU drivers that could be helpful in
determining if it's even feasible to try getting the GB drivers to
work?

I am getting a Galaxy Nexus (hopefully a 32GB GSM version if that ever
turns up) but it would still be nice to be able to experiment with the
N1.
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync cddykes10 14/11/11 18:11

ok thnx so much that helps much thank u

Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 14/11/11 18:22
I'd be surprised if GPU libraries crossed over easily from Galaxy
Nexus to Nexus S. Interestingly in fact, the GPU libraries that ship
on Galaxy Nexus don't work on PandaBoard, even though those are both
OMAP44x0 systems, and PandaBoard uses a specific set of libraries.

I don't have any deeper insight in the exact changes in the graphics
pipeline since Gingerbread, sorry.

JBQ

Re: ICS in AOSP: we're live, feel free to sync yjwong92 14/11/11 18:25
Hi,

Is there going to be a build configuration for Exynos? Or SMDK310.

Regards,
Wong Yong Jie

On Nov 15, 10:22 am, Jean-Baptiste Queru <j...@android.com> wrote:
> I'd be surprised if GPU libraries crossed over easily from Galaxy
> Nexus to Nexus S. Interestingly in fact, the GPU libraries that ship
> on Galaxy Nexus don't work on PandaBoard, even though those are both
> OMAP44x0 systems, and PandaBoard uses a specific set of libraries.
>
> I don't have any deeper insight in the exact changes in the graphics
> pipeline since Gingerbread, sorry.
>
> JBQ
>
>
>
>
>
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Conley Owens 14/11/11 18:30
On Mon, Nov 14, 2011 at 6:25 PM, yjwong92 <yjwo...@gmail.com> wrote:
> Hi,
>
> Is there going to be a build configuration for Exynos? Or SMDK310.

Sorry, but we can really only provide support for nexus devices.

Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 14/11/11 18:30
The build configurations in AOSP are based on the flagship devices
that Google is involved in, and no flagship devices were based on
those chips. You'd have to ask the manufacturers of those chips to
provide the appropriate source files.

Thanks,
JBQ

Re: ICS in AOSP: we're live, feel free to sync einmus 14/11/11 18:51
It turns out I used repo from previous android .repo/repo/repo. If you
use a fresh repo. It'll be fine.
> >>http://code.google.com/**android/nexus/drivers.html<http://code.google.com/android/nexus/drivers.html>
>
> >> JBQ
>
> > --
> > Dominic Binks: dbi...@codeaurora.org
> > Employee of Qualcomm Innovation Center, Inc.
> > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > --
> > 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<android-...@googlegroups.com>
> > To unsubscribe from this group, send email to
> > android-building+unsubscribe@**googlegroups.com<android-building%2Bunsubscribe@googlegroups.com>
> > For more options, visit this group at
Re: [android-building] ICS in AOSP: we're live, feel free to sync Matt Oakes 15/11/11 03:55
Does this mean we will be getting support for crespo in ASOP ICS in the future?
Re: ICS in AOSP: we're live, feel free to sync blunden 14/11/11 19:15
Very interesting indeed. I didn't know that.

Since I've never seen that kind of thing documented, I would assume
one has to try to determine it using the "staring at code"
approach. ;)

Do you have any idea if the emulator drivers would work to give
software rendering at least (I know it would be dirt slow)? If so,
that would at least allow it to boot up and allow you to try the newer
build.

On 15 Nov, 03:22, Jean-Baptiste Queru <j...@android.com> wrote:
> I'd be surprised if GPU libraries crossed over easily from Galaxy
> Nexus to Nexus S. Interestingly in fact, the GPU libraries that ship
> on Galaxy Nexus don't work on PandaBoard, even though those are both
> OMAP44x0 systems, and PandaBoard uses a specific set of libraries.
>
> I don't have any deeper insight in the exact changes in the graphics
> pipeline since Gingerbread, sorry.
>
> JBQ
>
>
>
>
>
> On Mon, Nov 14, 2011 at 6:10 PM, blunden <blund...@gmail.com> wrote:
> > Any reason the Galaxy Nexus GPU drivers wouldn't work for the Nexus S?
> > It is the same GPU after all, albeit with a much lower clock speed and
> > I assume that doesn't get set by the GPU driver.
>
> > Also, is there any documentation for the changes you implemented in
> > ICS compared to GB for the GPU drivers that could be helpful in
> > determining if it's even feasible to try getting the GB drivers to
> > work?
>
> > I am getting a Galaxy Nexus (hopefully a 32GB GSM version if that ever
> > turns up) but it would still be nice to be able to experiment with the
> > N1.
>
> > On 15 Nov, 02:51, Jean-Baptiste Queru <j...@android.com> wrote:
> >> I don't expect that you'll be able to easily run ICS with the GB
> >> graphics drivers for Nexus S, and if you get the basic system running
> >> you'll probably run into some "interesting" performance issues.
>
> >> JBQ
>
> >> On Mon, Nov 14, 2011 at 5:17 PM, David Wang <dwa...@gmail.com> wrote:
>
> >> > Are the proprietary graphics binaries needed to support hardware
> >> > acceleration?
>
> >> > Meaning if I wanted to get this to run on my Nexus S, would I need the
> >> > nexus S 4.0 graphics binaries in order to get the hardware
> >> > acceleration features of ICS?
>
> >> > On Nov 14, 3:19 pm, Jean-Baptiste Queru <j...@android.com> wrote:
>
> >> >> -Proprietary binaries for 4.0.1 will be available in the next few
> >> >> hours from their usual locationhttp://code.google.com/android/nexus/drivers.html
>
> >> >> 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
>
> >> --
> >> 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.
>
> > --
> > 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
> 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.
Re: ICS in AOSP: we're live, feel free to sync Michael Payne 14/11/11 20:21
Not to be a naysayer, but I was really looking forward to building for
the Nexus S.  Are the binaries going to be following soon?  I really
don't want my first build on my PandaBoard :/
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 15/11/11 09:06
It's all tied to having a consumer-ready build for Nexus S, and we're
still polishing that build.

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

> --
> 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
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.

Re: ICS in AOSP: we're live, feel free to sync Bzbit 15/11/11 00:29
This is great news!!

Can somone please tell me what kernel is used for ICS and where to
clone it from.
I like to build the kernel from source.

Thx

On Nov 15, 4:51 am, einmus <ein...@gmail.com> wrote:
> It turns out I used repo from previous android .repo/repo/repo. If you
> use a fresh repo. It'll be fine.
>
> On Nov 15, 7:26 am, Manish Shakya <manishshakya...@gmail.com> wrote:
>
>
>
> > I am seeing following error
> > Initializing project platform/abi/cpp ...
> > 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
>
> > On Mon, Nov 14, 2011 at 6:22 PM, Dominic Binks <dbi...@codeaurora.org>wrote:
>
> > > Hi JBQ,
>
> > > 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
>
> > > On 11/14/2011 3:19 PM, Jean-Baptiste Queru wrote:
>
> > >> You can go ahead and sync ICS from AOSP.
>
> > >> 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<http://code.google.com/android/nexus/drivers.html>
>
> > >> JBQ
>
> > > --
> > > Dominic Binks: dbi...@codeaurora.org
> > > Employee of Qualcomm Innovation Center, Inc.
> > > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > > --
> > > 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<android-...@googlegroups.com>
> > > To unsubscribe from this group, send email to
> > > android-building+unsubscribe@**googlegroups.com<android-building%2Bunsubscr­i...@googlegroups.com>
> > > For more options, visit this group at
> > >http://groups.google.com/**group/android-building?hl=en<http://groups.google.com/group/android-building?hl=en>
>
> > --
> > Manish Shakyahttp://www.manishshakya.com.nphttp://secs.oakland.edu/~ganesan/iMX/- Hide quoted text -
>
> - Show quoted text -
Re: ICS in AOSP: we're live, feel free to sync Ne0 15/11/11 01:58
JQB,

So does this mean i can't sync from a previous repo? I tried and get
the same issue.

On Nov 14, 11:27 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> You need a recent version of repo, 1.7.7 or newer, to be able to parse
> the new AOSP manifests.
>
> curlhttps://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
> >>http://code.google.com/android/nexus/drivers.html
>
> >> JBQ
>
> > --
> > Dominic Binks: dbi...@codeaurora.org
> > Employee of Qualcomm Innovation Center, Inc.
> > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > --
> > 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
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 15/11/11 09:39
If that's a previous repo from the new servers (that have been online
for a few weeks), that should be all transparent.

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

Re: [android-building] ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 15/11/11 09:40
That's all tied to having a consumer release, really, so it depends on
what happens on that front, which isn't something that I'm involved
in.

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?
>
> --
> 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
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.

Re: ICS in AOSP: we're live, feel free to sync Brandon 15/11/11 06:06
Will this include the source code for Google TV?  I apologize if this
has been covered elsewhere, I have not been able to find any
information about it.
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 15/11/11 09:54
Google TV is an entirely separate project, with their own release
processes and schedules, and I have no visibility over their plans.

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
>

--
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.

Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Matt Oakes 15/11/11 09:13

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 :-)

Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Jean-Baptiste Queru 15/11/11 10:01
My crystal ball is really foggy, so I can't predict the future
precisely enough to have any such estimate, sorry.

JBQ

Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Matt Oakes 15/11/11 10:05

It seems mines fairly good. I predicted that would be the answer ;-)

Re: ICS in AOSP: we're live, feel free to sync powder366 15/11/11 12:04

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

On Nov 15, 3:51 am, einmus <ein...@gmail.com> wrote:
> It turns out I used repo from previous android .repo/repo/repo. If you
> use a fresh repo. It'll be fine.
>
> On Nov 15, 7:26 am, Manish Shakya <manishshakya...@gmail.com> wrote:
>
>
>
>
>
>
>
> > I am seeing following error
> > Initializing project platform/abi/cpp ...
> >fatal: '../platform/abi/cpp.git'doesnotappearto be agitrepository
> >fatal: The remote end hung up unexpectedly
> > error: Cannot fetch platform/abi/cpp
>
> > On Mon, Nov 14, 2011 at 6:22 PM, Dominic Binks <dbi...@codeaurora.org>wrote:
>
> > > Hi JBQ,
>
> > > I'm seeing this error - am I being stupid (again) or is something missing?
>
> > >fatal: '../platform/abi/cpp.git'doesnotappearto be agitrepository
> > >fatal: The remote end hung up unexpectedly
> > > error: Cannot fetch platform/abi/cpp
>
> > > On 11/14/2011 3:19 PM, Jean-Baptiste Queru wrote:
>
> > >> You can go ahead and sync ICS from AOSP.
>
> > >> I strongly recommend syncing new clients: our implementation ofgit
> > >> 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 mightnotbe 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'snot100% 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<http://code.google.com/android/nexus/drivers.html>
>
> > >> JBQ
>
> > > --
> > > Dominic Binks: dbi...@codeaurora.org
> > > Employee of Qualcomm Innovation Center, Inc.
> > > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
> > > --
> > > 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<android-...@googlegroups.com>
> > > To unsubscribe from this group, send email to
> > > android-building+unsubscribe@**googlegroups.com<android-building%2Bunsubscr i...@googlegroups.com>
> > > For more options, visit this group at
Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Magnus Bäck 15/11/11 13:16
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

Re: [android-building] Re: ICS in AOSP: we're live, feel free to sync Xianghua Xiao 15/11/11 14:18
panda built completed smoothly here, 32 minutes on i7 machine with -j8.
xianghua

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
> http://groups.google.com/group/android-building?hl=en
>

Re: ICS in AOSP: we're live, feel free to sync Michael Payne 16/11/11 11:56
Thanks for the explanation, Jean-Baptiste.  Looking forward to the
binaries, as well as the Galaxy heading to me in the mail.

On Nov 15, 9:06 am, Jean-Baptiste Queru <j...@android.com> wrote:
> It's all tied to having a consumer-ready build for Nexus S, and we're
> still polishing that build.
>
> 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
>
> On Mon, Nov 14, 2011 at 8:21 PM, Michael Payne
>
Plus de sujets »