After fixing some of the issues I'm running into a problem that even the latest Google Play Services library is using deprecated and removed features (API 23) [1]. Unfortunately this is partial related to our build system including the big all-inclusive library JAR instead of the more granular AARs. It seems like we'll have to wait until Google ships an update for that.
If you are stuck with support library 23: After looking into what the SDK updater does I've been able to restore my local version of the support library by downloading and extracting this zip [2] into $ANDROID_HOME/extras/android/ (This is hacky. Proceed at your own risk.) [1]: https://pastebin.mozilla.org/8843080 [2]: https://dl.google.com/android/repository/support_r22.2.1.zip On Tue, Aug 18, 2015 at 2:49 PM, Sebastian Kaspari <[email protected]> wrote: > Hey everyone, > > with the release of the final Android SDK 23 the Android team also > released a new version of the support libraries (23.0). > > Building with this new support library (actually the appcompat library) > will break the mach-based build (bug 1195691 [1]) as long as you are not > building with the new Android SDK 23. But doing so will introduce a whole > new set of issues (bug 1183061 [2]). Unfortunately our build system will > always pick the latest, locally available support library (not like the > gradle build with a pinned version) and so there's not really a way back. > > There are a bunch of things we need to do in order to build with the new > SDK. Currently I'm focusing on just build errors (removed or deprecated > APIs). With those fixed we can at least build locally with the new SDK. > > Sebastian > > P.S.: You might see a build error regarding google play services if you > are building with gradle. We bumped the version in build.gradle yesterday > [3] so you might need to update the "Google repository" and it might be > tempting to update the support library too while you are at it. So this > mail should be a warning. ;) > > P.P.S.: Afaik we only build with the appcompat library if > MOZ_NATIVE_DEVICES is set. So disabling this might be a workaround if you > already updated the library. (Untested) > > [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1195691 > [2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1183061 > [3]: http://hg.mozilla.org/integration/fx-team/rev/7bbb08844061 >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
