-Gingerbread requires a 64-bit JDK 1.6 (which implies that you need a
64-bit host to build it). The instructions at source.android.com are
outdated, and 64-bit Ubuntu 10.4 is the preferred environment. We'll
be updating those instructions in the coming weeks.
-You should expect that Gingerbread will use at least 12GB of disk
space after syncing and building. The number will be higher if you
build for multiple hardware targets.
-Android likes to be built on machines with lots of RAM. There are
benefits up to at least 12GB of RAM (and more if you routinely work in
multiple branches simultaneously).
-The toolchain in android-2.3_r1 is known to work well for ARMv7
targets, but it sometimes generates incorrect ARMv5 code. The
toolchain in the gingerbread branch contains a fix for the ARMv5 code
generation, but hasn't been tested nearly as much.
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.
thanks,
-Jey
> --
> 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
On the same note, Would 32-bit Ubuntu host be un-supported on Gingerbread?
Wondering what would be your recommendation to handle two builds
(post/pre Gingerbread) on the same linux machine.
thanks,
-Jey
In that case, the envsetup.sh from gingerbread will switch to the 1.6
JDK. Caveat: once you do that in a terminal, you won't be able to use
the same terminal for froyo any more.
JBQ
Thanks again.
-Jey
I've downloaded and built the gingerbread source (thanks!). I executed the
resulting system.img on the emulator and it works.
Now I'm trying to set up my Eclipse environment. I decided to take a walk
on the wild side and use Eclipse version "Helios" (3.6.1-linux-gtk-x86_64)
configured to use JRE java-6-sun-1.6.0.22.
I am following the instructions on
http://source.android.com/source/using-eclipse.html.
The first stumbling block is when you reach this step:
5. Select "Create project from existing source", enter the path...
There is no "Create project from existing source" option in Helios. I found
some instructions on the net that said:
uncheck the "Use default location" box.
browse to the location where you extracted the source
# I assumed this is the directory where I copied the .classpath file
I hit "Finish" and the wizard and Eclipse just sat there a long time and
then correctly populated my workspace.
But there was a red exclamation point next to my project in the package
explorer and in the Problems window there are 3 errors:
project 'ginger' is missing required library:
'out/target/common/obj/JAVA_LIBRARIES/google-common-intermediates/javalib.ja
r
project 'ginger' is missing required library:
'out/target/common/obj/JAVA_LIBRARIES/gsf-client-intermediates/javalib.jar
The project cannot be built until build path errors are resolved.
Recalling that I had a similiar experience with froyo
(http://groups.google.com/group/android-building/browse_thread/thread/217007
0bd7b81302), I followed the instructions there:
In the "Libraries" tab of the Java Build Path:
- Remove those two .jar files from my build path
- add this .jar to the build path:
out/target/common/obj/JAVA_LIBRARIES/android-common_intermediates/javalib.ja
r
hit ok
Everything compiles cleanly. Thanks.
-Sam
On my machine, JDK 1.5 is installed in 64-bit, but I don't remember
whether that was a hard requirement or not.
JBQ
-This hasn't been tested by Google. While unlikely, there's a
possibility that subtle differences in the toolchain could creep up as
bugs.
-If you're sharing your source tree with other people, you need to be
very careful to not use @Override on interface methods, as JDK 1.5
doesn't support that.
JBQ