StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>Update for Android Studio 1.0</strong></p> <p>Since Android Studio 1.0 was released (and a lot of versions between v1.0 and one of the firsts from the time of my previous answer) some things has changed.</p> <p>My description is focused on adding external library project by hand via Gradle files (for better understanding the process). If you want to add a library via Android Studio creator just check <a href="https://stackoverflow.com/a/16634680/2021293">the answer</a> below with visual guide (there are some differences between Android Studio 1.0 and those from screenshots, but the process is very similar).</p> <p>Before you start adding a library to your project by hand, consider adding the external dependency. It won’t mess in your project structure. Almost every well-known Android library is available in a <a href="http://en.wikipedia.org/wiki/Apache_Maven" rel="noreferrer">Maven</a> repository and its installation takes only one line of code in the <code>app/build.gradle</code> file:</p> <pre><code>dependencies { compile 'com.jakewharton:butterknife:6.0.0' } </code></pre> <p><strong>Adding the library</strong></p> <p>Here is the full process of adding external Android library to our project:</p> <ol> <li>Create a new project via Android Studio creator. I named it <em>HelloWorld</em>.</li> <li>Here is the original project structure created by Android Studio:</li> </ol> <blockquote> <pre><code>HelloWorld/ app/ - build.gradle // local Gradle configuration (for app only) ... - build.gradle // Global Gradle configuration (for whole project) - settings.gradle - gradle.properties ... </code></pre> </blockquote> <ol start="3"> <li>In the root directory (<code>HelloWorld/</code>), create new folder: <code>/libs</code> in which we’ll place our external libraries (this step is not required - only for keeping a cleaner project structure).</li> <li>Paste your library in the newly created <code>/libs</code> folder. In this example I used <a href="https://github.com/astuetz/PagerSlidingTabStrip" rel="noreferrer">PagerSlidingTabStrip library</a> (just download ZIP from GitHub, rename library directory to „PagerSlidingTabStrip" and copy it). Here is the new structure of our project:</li> </ol> <blockquote> <pre><code>HelloWorld/ app/ - build.gradle // Local Gradle configuration (for app only) ... libs/ PagerSlidingTabStrip/ - build.gradle // Local Gradle configuration (for library only) - build.gradle // Global Gradle configuration (for whole project) - settings.gradle - gradle.properties ... </code></pre> </blockquote> <ol start="5"> <li><p>Edit settings.gradle by adding your library to <code>include</code>. If you use a custom path like I did, you have also to define the project directory for our library. A whole settings.gradle should look like below:</p> <pre><code>include ':app', ':PagerSlidingTabStrip' project(':PagerSlidingTabStrip').projectDir = new File('libs/PagerSlidingTabStrip') </code></pre></li> </ol> <p>5.1 If you face "Default Configuration" error, then try this instead of step 5,</p> <pre><code> include ':app' include ':libs:PagerSlidingTabStrip' </code></pre> <ol start="6"> <li><p>In <code>app/build.gradle</code> add our library project as an dependency:</p> <pre><code>dependencies { compile fileTree(dir: 'libs', include: ['*.jar']) compile 'com.android.support:appcompat-v7:21.0.3' compile project(":PagerSlidingTabStrip") } </code></pre></li> </ol> <p>6.1. If you followed step 5.1, then follow this instead of 6,</p> <pre><code> dependencies { compile fileTree(dir: 'libs', include: ['*.jar']) compile 'com.android.support:appcompat-v7:21.0.3' compile project(":libs:PagerSlidingTabStrip") } </code></pre> <ol start="7"> <li><p>If your library project doesn’t have <code>build.gradle</code> file you have to create it manually. Here is example of that file:</p> <pre><code> apply plugin: 'com.android.library' dependencies { compile 'com.android.support:support-v4:21.0.3' } android { compileSdkVersion 21 buildToolsVersion "21.1.2" defaultConfig { minSdkVersion 14 targetSdkVersion 21 } sourceSets { main { manifest.srcFile 'AndroidManifest.xml' java.srcDirs = ['src'] res.srcDirs = ['res'] } } } </code></pre></li> <li><p>Additionally you can create a global configuration for your project which will contain SDK versions and build tools version for every module to keep consistency. Just edit <code>gradle.properties</code> file and add lines:</p> <pre><code>ANDROID_BUILD_MIN_SDK_VERSION=14 ANDROID_BUILD_TARGET_SDK_VERSION=21 ANDROID_BUILD_TOOLS_VERSION=21.1.3 ANDROID_BUILD_SDK_VERSION=21 </code></pre> <p>Now you can use it in your <code>build.gradle</code> files (in app and libraries modules) like below:</p> <pre><code>//... android { compileSdkVersion Integer.parseInt(project.ANDROID_BUILD_SDK_VERSION) buildToolsVersion project.ANDROID_BUILD_TOOLS_VERSION defaultConfig { minSdkVersion Integer.parseInt(project.ANDROID_BUILD_MIN_SDK_VERSION) targetSdkVersion Integer.parseInt(project.ANDROID_BUILD_TARGET_SDK_VERSION) } } //... </code></pre></li> <li><p>That’s all. Just click‚ synchronise the project with the Gradle’ icon <img src="https://i.stack.imgur.com/QH01w.png" alt="synchronise with Gradle">. Your library should be available in your project.</p></li> </ol> <p><em><a href="http://www.youtube.com/watch?v=LCJAgPkpmR0" rel="noreferrer">Google I/O 2013 - The New Android SDK Build System </a></em> is a great presentation about building Android apps with Gradle Build System: As Xavier Ducrohet said:</p> <blockquote> <p>Android Studio is all about editing, and debugging and profiling. It's not about building any more.</p> </blockquote> <p>At the beginning it may be little bit confusing (especially for those, who works with <a href="http://en.wikipedia.org/wiki/Eclipse_%28software%29" rel="noreferrer">Eclipse</a> and have never seen the ant - like me ;) ), but at the end Gradle gives us some great opportunities and it worth to learn this build system.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload