How does https://download-chromium.appspot.com/?platform=Android build Chromium?

[Shengbin Meng]

Hi, does anyone know how the website "https://download-chromium.appspot.com/?platform=Android" build Chromium?

Is there any difference from what says on the instruction page (https://code.google.com/p/chromium/wiki/AndroidBuildInstructions)?

I ask because I myself can never build a ChromeShell.apk the same with that downloaded from there. The apk I downloaded works well for a WebRTC app but the apk I built doesn't work.

What may go wrong?

[Primiano Tucci]

> Is there any difference from what says on the instruction page (https://code.google.com/p/chromium/wiki/AndroidBuildInstructions)?

Short answer: it shouldn't

Longer answer

That page fetches the builds from:

https://commondatastorage.googleapis.com/chromium-browser-snapshots/Android/NNNN/chrome-android.zip  (NNNN = cr-commit-position of ToT at the time of build)

In turn that GCS bucket is fed by this bot in the archive_build step:

http://build.chromium.org/p/chromium/builders/Android/

The GYP_DEFINES used by that bot (See the slave_steps stdio) are just

GYP_DEFINES=' OS=android fastbuild=1' (goma is irrelevant)

Probably you synced the code at a time when WebRTC wasn't working?

Are you building from the out/Release folder?

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

--

Primiano Tucci
Software Engineer
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W 9TQ

[Shengbin Meng]

Thanks for the explanation.

> Probably you synced the code at a time when WebRTC wasn't working?

Oh, this might be the problem. I did a fetch&sync about a year ago. Recently I noticed the following in the instruction page and did as it said (I am indeed reusing a desktop checkout).

NOTE: if didn't do fetch android to get your code (e.g. you're reusing a desktop checkout), you'll likely need to do:

~/chromium$ echo "target_os = ['android']" >> .gclient && gclient sync

But somehow the code doesn't get up-to-date! Git log shows that the commits still remain at last year. Do you know why is that?

Now I am doing a fresh new `fetch android`, and hope it works.

> Are you building from the out/Release folder?

I am executing exactly the following command if that's what you mean.

~/chromium/src$ ninja -C out/Release chrome_shell_apk

Thanks again.

[Primiano Tucci]

gclient sync doesn't update the code, just synchronizes the rest of the subprojects to be consistent with DEPS of the mainprojects (think to gclient sync as to a "git submodules update").

What you want to do is:

git pull (or git remote update && git reset --hard origin/master && git clean -df, depending on the cleanliness of your checkout)

gclient sync

[Shengbin Meng]

Got it. Thank you.