538524 - (releng-android) [Tracking bug] officially support Android builds

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Aki Sasaki (not active)]

Taking for now.

Comment 1

[Chris Cooper [:coop] (he/him)]

Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.

Comment 2

[Brian Carpenter [:geeknik]]

Are there any builds available anywhere for download? I've been a nightly Firefox trunk tester for a couple of years now, so installing something that isn't even alpha quality doesn't scare me. Much. ;)

Comment 3

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

(Copied from email)


0. Install a JDK -- CentOS package java-1.6.0-openjdk-devel seems to work,
   though you can also install a Sun JDK from http://java.sun.com/javase/downloads/index.jsp .  openjdk package is probably easier given that the builders are CentOS (there's an equivalent Ubuntu package as well).

1. Grab linux sdk from http://developer.android.com/sdk/index.html
  --> http://dl.google.com/android/android-sdk_r05-linux_86.tgz

2. Grab linux ndk from http://developer.android.com/sdk/ndk/index.html
  --> http://dl.google.com/android/ndk/android-ndk-r3-linux-x86.zip

3. Everything will be done relative to ~/android -- this directory can be anywhere/named anything, as long as the paths in the mozconfig are correct.

4. Untar the sdk in ~/android, producing ~/android/android-sdk-linux_x86

5. Unzip the ndk in ~/android, producing ~/android/android-ndk-r3

6. With an X server (VNC works fine), in the ~/android/android-sdk-linux_x86 directory, run tools/android -- no way to do the install from the command line that I can find
   - under Available Packages, select Android SDK, API levels 4 6 and 7 (for android 1.6, 2.0.1, and 2.1)
   - close down the android sdk tool after installation

7. current hg repo is at http://hg.mozilla.org/users/vladimir_mozilla.com/mozilla-droid

NOTE: current hg repo build will die while building widget; we have a temporary dependency on having access to the raw Gecko sources.  This will be going away very soon.

7.1: check out fennec mobile repo into mozilla-droid/mobile, if fennec is to be built

7.2. ensure working dir in source tree is on the android branch, not default

8. mozconfig (note: no xulrunner for fennec; firefox difference is just --enable-application=browser):

=== begin ===

ac_add_options --enable-application=mobile

ac_add_options --disable-ogg
ac_add_options --disable-wave

ac_add_options --with-arm-kuser

# Global options
ac_add_options --disable-debug
ac_add_options --enable-optimize
ac_add_options --enable-libxul

# mobile options
ac_add_options --disable-installer
ac_add_options --disable-crashreporter
ac_add_options --disable-printing
ac_add_options --disable-javaxpcom

# android options
ac_add_options --target=arm-android-eabi

ac_add_options --with-android-ndk=/home/cltbld/android/android-ndk-r3
ac_add_options --with-android-sdk=/home/cltbld/android/android-sdk-linux_86/platforms/android-6
ac_add_options --with-android-tools=/home/cltbld/android/android-sdk-linux_86/tools

ac_add_options --with-endian=little
ac_add_options --enable-tree-freetype
ac_add_options --enable-faststripe

# other options
ac_add_options --disable-necko-wifi
ac_add_options --disable-plugins

# to fix
#ac_add_options --disable-crypto
# ssltunnel can't build if we disable crypto
ac_add_options --disable-tests

=== end ===

9. build with above mozconfig

NOTE: see above about build dying in widget; will be fixed soon.

10. When build finishes, run make in embedding/android

11. Final package is embedding/android/gecko.apk

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Pushing over to bear.

Comment 5

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

The widget rendering issue is fixed; there's now no dependency on the android source release.  Builds as described above should complete with the latest mozilla-droid repo tree.

Comment 6

[Robert Sayre]

shouldn't we target 2.1+ only at this point?

Comment 7

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to comment #6)
> shouldn't we target 2.1+ only at this point?

Fine by me, but best for Stuart and Vlad to answer. It would simplify life if we could do 2.1 and ignore 2.0, 1.5...

Comment 8

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

Ignore that; for our purposes, there's no difference between 2.0 and 2.1.

Comment 9

[Robert Sayre]

(In reply to comment #8)
> Ignore that; for our purposes, there's no difference between 2.0 and 2.1.

Do you mean support 2.1 only?

Comment 10

[Stuart Parmenter]

We are aiming to currently support Android 2.0+ for our product releases.  As we won't be shipping a final release for a while, that may change over time to newer versions if we need newer OS features.

Comment 11

[Robert Sayre]

If you aren't going to ship for a while, why would you blow up the QA matrix with Android 2.0? Do you think it is going to be relevant when you ship? If so, why?

Comment 12

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

Guys, wrong place for this discussion.  The build information here is independent of whether we decide to officially support/not support 2.0/2.1/whatever.

Comment 13

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

Also, unless something extreme happens, we won't be supporting Android 1.x.  There's no point, given the hardware situation there.

Comment 14

[Aki Sasaki (not active)]

I think these are officially supported.
This is a tracking bug tracking two tracking bugs; resolving.