{"id":358,"date":"2014-10-11T02:46:38","date_gmt":"2014-10-11T00:46:38","guid":{"rendered":"http:\/\/blogs.igalia.com\/eocanha\/?p=358"},"modified":"2014-10-11T02:46:38","modified_gmt":"2014-10-11T00:46:38","slug":"hacking-on-chromium-for-android-from-eclipse-part-1","status":"publish","type":"post","link":"https:\/\/eocanha.org\/blog\/2014\/10\/11\/hacking-on-chromium-for-android-from-eclipse-part-1\/","title":{"rendered":"Hacking on Chromium for Android from Eclipse (part 1)"},"content":{"rendered":"

In the Chromium Developers<\/a> website has some excellent resources on how to setup an environment to build Chromium for Linux desktop<\/a> and for Android<\/a>. There’s also a detailed guide on how to setup Eclipse as your development environment<\/a>, enabling you to take advantage of code indexing and enjoy features such as type hierarchy, call hierarchy, macro expansion, references and a lot of tools much better than the poor man’s trick of grepping the code.<\/p>\n

Unfortunately, there are some integration aspects not covered by those guides, so joining all the dots is not a smooth task. In this series of posts, I’m going to explain the missing parts to setup a working environment to code and debug Chromium for Android from Eclipse, both C++ and Java code. All the steps and commands from this series of posts have been tested in an Ubuntu Saucy chroot. See my previous post on how to setup a chroot<\/a> if you want to know how to do this.<\/p>\n

Get the source code<\/strong><\/p>\n

See the get-the-code<\/a> guide.\u00a0Don’t try to reconvert a normal Desktop build into an Android build. It just doesn’t work. The detailed steps to get the code from scratch and prepare the dependencies are the following:<\/span><\/p>\n

 cd ANDROID # Or the directory you want\n fetch --nohooks android --nosvn=True\n cd src\n git checkout master\n build\/install-build-deps.sh\n build\/install-build-deps-android.sh\n gclient sync --nohooks<\/pre>\n
Configure and generate the project (see AndroidBuildInstructions<\/a>), from src:<\/p>\n
 # Make sure that ANDROID\/.gclient has this line:\n # target_os = [u'android']\n # And ANDROID\/chromium.gyp_env has this line:\n # { 'GYP_DEFINES': 'OS=android', }\n gclient runhooks<\/pre>\n
Build Chrome shell, from src:<\/p>\n
 # This builds\n ninja -C out\/Release chrome_shell_apk\n # This installs in the device\n # Remember the usual stuff to use a new device with adb:\n # http:\/\/developer.android.com\/tools\/device.html \n # http:\/\/developer.android.com\/tools\/help\/adb.html#Enabling\n # Ensure that you can adb shell into the device\n build\/android\/adb_install_apk.py --apk ChromeShell.apk --release<\/pre>\n
If you ever need to update the source code, follow this recipe and use Release or Debug at your convenience:<\/p>\n
 git pull origin master\n gclient sync\n # ninja -C out\/Release chrome_shell_apk\n ninja -C out\/Debug chrome_shell_apk\n # build\/android\/adb_install_apk.py --apk ChromeShell.apk --release\n build\/android\/adb_install_apk.py --apk ChromeShell.apk --debug<\/pre>\n
As a curiosity, it’s worth to mention that adb<\/strong> is installed on third_party\/android_tools\/sdk\/platform-tools\/adb.<\/p>\n
Configure Eclipse<\/strong><\/p>\n
To configure Eclipse, follow the instructions in LinuxEclipseDev<\/a>. They work nice with Eclipse Kepler.<\/p>\n
In order to open and debug the Java code properly, it’s also interesting to install the ADT plugin in Eclipse <\/a>too.\u00a0Don’t try to reuse the Android SDK in “third_party\/android_tools\/sdk”. It seems to lack some things. Download a fresh standalone SDK from the official page<\/a>\u00a0instead and tell the ADT plugin to use it.<\/p>\n
In the next post, I will explain how to debug C++ code running in the device, both from the command line and from Eclipse.<\/p>\n
\"chromium_android_eclipse_cpp\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
In the Chromium Developers website has some excellent resources on how to setup an environment to build Chromium for Linux desktop and for Android. There’s also a detailed guide on how to setup Eclipse as your development environment, enabling you to take advantage of code indexing and enjoy features such as type hierarchy, call hierarchy, … Continue reading Hacking on Chromium for Android from Eclipse (part 1)<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[8,9,2,7],"tags":[],"_links":{"self":[{"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/posts\/358"}],"collection":[{"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/comments?post=358"}],"version-history":[{"count":0,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/posts\/358\/revisions"}],"wp:attachment":[{"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/media?parent=358"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/categories?post=358"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eocanha.org\/blog\/wp-json\/wp\/v2\/tags?post=358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}