Update ndk sysroot to API level 14

Update ndk sysroot to API level 14.

Update ndk toolchain to api level 14 to make application to be
able to setup SL_ANDROID_RECORDING_PRESET_VOICE_COMMUNICATION
mode which was introduced in api level 14 in opensl.

BUG=179926
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=186254

[digit1, 2013-03-04 18:38:05]

Thanks. LGTM

Please fix the typo in the comment message, and add a small comment explaining
that API level 14 is ICS (Android 4.0) which is the minimum platform requirement
for Chrome on Android.

[Yaron, 2013-03-04 19:20:11]

It looks like you missed a few places:
tools/clang/scripts/update.sh
and also build/android.gypi (in v8) but that'll be a separate commit. I'll send
a try job for android-clang which I assume will fail.

Pardon my ignorance but what's the implications of making this change? Are we
really using android api level 9 from the ndk instead of 14? It also looks like
there were no versions between 9 and 14? Were there no updates in between? Also,
in general a brief description of motivation for the change should be in cl
description.

[digit1, 2013-03-04 22:05:35]

To answer a few of Yaron's statements:


On Mon, Mar 4, 2013 at 8:20 PM, <yfriedman@chromium.org> wrote:

> It looks like you missed a few places:
> tools/clang/scripts/update.sh
> and also build/android.gypi (in v8) but that'll be a separate commit. I'll
> send
> a try job for android-clang which I assume will fail.
>
> Pardon my ignorance but what's the implications of making this change? Are
> we
> really using android api level 9 from the ndk instead of 14?


Yes, Chrome has been using the API level 9 *native* APIs since the start of
the project, the level 14 APIs were only exposed after our little project
started.
Also, keep in mind that is only related to the native APIs (we still depend
on Java APIs from level 14 or higher).


> It also looks like
> there were no versions between 9 and 14? Were there no updates in between?


Yes, there were no updates to the native APIs between these platform
releases. The NDK doesn't have its own API level (which is a good thing,
the opposite would be very confusing with very little benefits).


> Also,
> in general a brief description of motivation for the change should be in cl
> description.
>
>
https://codereview.chromium.**org/12379078/<https://codereview.chromium.org/1...
>

[Yaron, 2013-03-04 23:08:02]

On 2013/03/04 22:05:35, digit1 wrote:
> To answer a few of Yaron's statements:
> 
> 
> On Mon, Mar 4, 2013 at 8:20 PM, <mailto:yfriedman@chromium.org> wrote:
> 
> > It looks like you missed a few places:
> > tools/clang/scripts/update.sh
> > and also build/android.gypi (in v8) but that'll be a separate commit. I'll
> > send
> > a try job for android-clang which I assume will fail.
> >
> > Pardon my ignorance but what's the implications of making this change? Are
> > we
> > really using android api level 9 from the ndk instead of 14?
> 
> 
> Yes, Chrome has been using the API level 9 *native* APIs since the start of
> the project, the level 14 APIs were only exposed after our little project
> started.
> Also, keep in mind that is only related to the native APIs (we still depend
> on Java APIs from level 14 or higher).
> 
> 
> > It also looks like
> > there were no versions between 9 and 14? Were there no updates in between?
> 
> 
> Yes, there were no updates to the native APIs between these platform
> releases. The NDK doesn't have its own API level (which is a good thing,
> the opposite would be very confusing with very little benefits).
> 
> 
> > Also,
> > in general a brief description of motivation for the change should be in cl
> > description.
> >
> >
>
https://codereview.chromium.**org/12379078/%3Chttps://codereview.chromium.org...>
> >

Thanks, David. looks good once you update the clang file and cl description

[leozwang1, 2013-03-05 05:26:50]

PTAL, will commit tomorrow if there is no more problem.

[commit-bot: I haz the power, 2013-03-05 15:07:16]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/leozwang@chromium.org/12379078/4011

[commit-bot: I haz the power, 2013-03-05 16:37:59]

Retried try job too often on mac_rel for step(s) interactive_ui_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_rel&nu...

[commit-bot: I haz the power, 2013-03-05 19:51:02]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/leozwang@chromium.org/12379078/4011

[commit-bot: I haz the power, 2013-03-05 20:54:34]

Change committed as 186254