--
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
Check out one of the Froyo tags instead of the master branch:
For example:
repo init -u git://android.git.kernel.org/platform/manifest.git -b
android-2.2.1_r
repo sync
Thanks,
Anders
You can install ubuntu using wubi on your windows 7 computer. It installs ubuntu in a large file on your ntfs partition, and configures dual boot, so you can reboot into ubuntu.
Ketil
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post...
BR,
Przemek
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.
This question has been posed alot and I have posted that the patch to enforce 64bit builds be removed, but the response seems to be that google uses 64bit machines, so we have to as well.
I still think it is unnecessary, but you can make it work pretty easy
On Nov 17, 2010, at 5:08 PM, "Emeka Omo" <speed...@gmail.com<mailto:speed...@gmail.com>> wrote:
Actually that's not true. JDK comes in both 32-bit & 64-bit. You can find both at the Oracle SUN JAVA site.
The problem is that if you are using Eclipse; it will pick the same version of JDK as itself.
Eclipse 32-bit version will look for JDK 32-bit and Eclipse 64-bit version will look for JDK 64-bit version.
As for my post earlier; I have done cross platform compilation. In the context of Andriod; I have not found a workable solution of building 64-bit on a 32-bit machine.
Even if you do cross platform compilation; you still test it on an actually target machine.
Chris;
You might want to trying using VMWare workstation. I use that; it works great on an Intel i7 machine.
-Olisemeka
On Wed, Nov 17, 2010 at 2:50 PM, Jean-Baptiste Queru <<mailto:j...@android.com>j...@android.com<mailto:j...@android.com>> wrote:
The root reason is that JDK 1.6 is only available as 64-bit on some platforms.
JBQ
On Wed, Nov 17, 2010 at 2:46 PM, Przemyslaw Wegrzyn
<<mailto:pweg...@codepainters.com>pweg...@codepainters.com<mailto:pweg...@codepainters.com>> wrote:
> On 11/16/2010 07:30 PM, Ying Wang wrote:
>>
>> You only need 64-bit build machine for the master branch.
>
> Can anybody explain what is the rationale for this particular requirement?
> It seems that master branch compiles on 32-bit system with a bit of build
> env patching, so why was this requirement introduced really?
>
> BR,
> Przemek
>
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to <mailto:android-...@googlegroups.com> android-...@googlegroups.com<mailto:android-...@googlegroups.com>
> To unsubscribe from this group, send email to
> <mailto:android-building%2Bunsu...@googlegroups.com> android-buildi...@googlegroups.com<mailto:android-buildi...@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
>
--
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 <mailto:android-...@googlegroups.com> android-...@googlegroups.com<mailto:android-...@googlegroups.com>
To unsubscribe from this group, send email to
<mailto:android-building%2Bunsu...@googlegroups.com>android-buildi...@googlegroups.com<mailto:android-buildi...@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
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to <mailto:android-...@googlegroups.com> android-...@googlegroups.com<mailto:android-...@googlegroups.com>
To unsubscribe from this group, send email to
<mailto:android-buildi...@googlegroups.com>android-buildi...@googlegroups.com<mailto:android-buildi...@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
So, as with builds up to and including froyo, 32 bit build environments were the norm and 64 bit was not officially supported, as of Gingerbread the position reverses where 64 bit is the norm & 32 is officially unsupported.
It had to happen at some point because I vaguely recall hearing that under certain conditions running a build can push systems to the limits of the 32 bit RAM addressing on some platforms (I want to say a multi-threaded make on 32 bit Windows, but I'm not 100% certain) , so it was just a matter of when a change was made, and the when just happens to be now.
Al.
======
Funky Android Limited is registered in England & Wales with the company number 6741909.
The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
Even without per-process size limits, Android is a heavy piece of
software to compile, and typical 32-bit machines are unfortunately
quite impractical for such work.
JBQ
Could you please let me know what sort of problems I might find cross-compiling Windows SDK in a linux environment?
I'm doing it at the moment (and for Mac SDK as well) and the tests we ran on the packages created in this way show that it is usable and people that are experimenting it are happy. I haven't faced any support request yet that could be caused by the cross-compiled packages.
Regards,
Tiago
JBQ