here. As of Android Studio 1.4, Android Studio is aligning to the same model of releasing source code after each stable release. For those who contribute to Android Studio, the code contribution process is essentially the same as the Android platform. We expect to continue to release a stable version of Android Studio approximately every 2 -4 months, and at each of the these release the source code will be made available. Please continue to submit patches to the Android Studio AOSP branch. We will do code-reviews and merge changes into subsequent versions of Android Studio. We're incredibly grateful to all of you in the community for your collaboration and hard work on Android Studio.
We currently have the following possible branches for previous versions of Android Studio:
The branches ub-tools-idea133 and ub-tools-master are deprecated. We are also not using master.
For instance you can do a checkout of version 2.2.0 of the Gradle plugin with the following command:
$repo init -u https://android.googlesource.com/platform/manifest -b gradle_2.2.0
$ repo sync
The parts of the SDK that can be build with the studio-* branches are only the IDE components and the SDK Tools. Each component is build differently due to varying build systems.
None of them uses the make-based build system of the platform.
Historically, building the Android tools required building the full Android SDK as well, since for example the emulator needed the system image.
However, we've been gradually migrating the tools source code over to a more independent setup, and you can now build the Android Studio IDE without a full Android checkout and without a C compiler etc. The instructions for building Android Studio are listed in the Building Android Studio page; the remainder of this document documents the process for building the rest of the tools (the Eclipse plugin, the emulator, etc.)
For instructions, see Building the Android Gradle Plugin.
This part only builds the SDK Tools. Follow these steps:
$ mkdir -p out/dist
$ ./tools/buildSrc/servers/build_tools.sh `pwd`/out `pwd`/out/dist 1234
This will build the SDK Tools for your current platform. the result is located in out/sdk/
This is composed of
- The emulator and associated executables and libraries
- Java-based standalone tools
To work on the Java-based tools only, you can open the IJ project located in tools/base.
To build / test the java tools only:
$ cd tools/
$ ./gradlew assemble // builds only
$ ./gradlew check // runs tests as well.
Building the Windows SDK
These instructions are currently obsolete. Coming soon.
Full Windows SDK builds are only supported on Linux -- most of the framework is not designed to be built on Windows so technically the Windows SDK is build on top of a Linux SDK where a few binaries are replaced.
$ sudo apt-get install mingw32 tofrodos
$ . build/envsetup.sh
$ lunch sdk-eng
$ make win_sdk
Note that this will build both a Linux SDK then a Windows SDK. The result is located at
To set up your Eclipse environment to build, edit and debug the deprecated Eclipse plug-ins for Android, see the "Building the Eclipse-Based Tools" document.