Initially they’ll be enabled on an FYI bot, but will soon be moved to the CQ and main bots. chrome_public_apk is similar to chrome_shell_apk, but with even more features.Įxpected effect on bot times: The new tests take about 5 minutes to run. There are two important new build targets: chrome_public_apk and chrome_public_test_apk. – chrome/test/android/javatests_staging: will be merged into chrome/test/android/javatests in the nearish future – chrome/android/javatests: chrome/android/javatests_shell will be merged into here incrementally as ChromeShell tests are converted to run against ChromePublic – chrome/android/java_staging: will be merged into chrome/android/java in the nearish future This adds plenty of Android-specific code (Java, C++, and resources) in a few new folders: Upstream oodles of Chrome for Android code into Chromium.
Here is the description for the pertinent Chromium code review: A Chrome for Android software engineer posted on Reddit to say that “Chrome for Android is now almost entirely open-source.” The “almost” refers to licensing restrictions: media codecs and some of proprietary Google features can’t be included in Chromium.
Reddit user bongbongyeah asked: “When will we be able to build a fully fledged Chromium (not Chrome, i mean the Open Source counterpart) for Android?” The answer, courtesy of an Android Technical Program Manager, was straightforward: “Soon!” Last week, though, the Chrome for Android team held an AMA on Reddit, and we learned the tide would be turning. Until now, Chromium was largely a desktop-only affair.
0 kommentar(er)
