The app will appear on the device as "Chromium". Need to run 'gclient runhooks' again to get them in the build.**īuild/android/adb_install_apk.py out/Release/apks/ChromePublic.apk # For gyp.ĬHROMIUM_OUTPUT_DIR=$gndir build/android/adb_install_apk.py $gndir/apks/ChromePublic.apk # for gn. **Note: When adding new resource files or java files in gyp builds, you Which prints a list of connected devices.
Third_party/android_tools/sdk/platform-tools/adb devices You can check if the device is connected by running: You may also be prompted to allow access to your PC once your device is * Enable 'USB Debugging' and follow the prompts * Now navigate back to Settings \> Developer Options
* Navigate to Settings \> About Phone \> Build number Make sure your Android device is plugged in via USB, and USB Debugging 'chromium.gyp_env' with the following contents:Įcho "/`). # Configure GYP (deprecated - use GN instead) Both builds are regularly tested on the build waterfall. They are both meta-build systems that generate nina files for theĪndroid build. This is not needed for a typical developer workflow only for one-timeĪndroid builds can be run with GN or GYP, though GN incremental buildsĪre the fastest option and GN will soon be the only supported option. If you have an existing Linux checkout, you can add Android support byĪppending `target_os = ` to your. Then, if you have no existing checkout, create your source directory andįetch -nohooks android # This will take 30 minutes on a fast connection
Other (Mac/Windows) platforms are not supported for Android.įirst, check out and install the [depot\_tools