Android Studio: the correct method for importing projects and modules. androidproject
Gradle Project, Module Import
Recently, many people complained on the Internet that it is difficult for Android Studio to import some projects downloaded from github, including:
1. Import Gradle
2. No import
Next I will explain the correct import posture in two parts:
1. Import the complete Github Project
We are looking for a project on github.
# Wed Apr 10 15:27:10 PDT 2013 distributionBase = GRADLE_USER_HOMEdistributionPath = wrapper/distszipStoreBase = GRADLE_USER_HOMEzipStorePath = wrapper/distsdistributionUrl = http \:/logs
The author uses gradle-1.12-all.zip, and we open this directory C: \ Users \ Administrator \. gradle \ wrapper \ dists \ gradle-2.1-all \ 27drb4udbjf4k88eh2ffdc0n55
We use gradle-2.1-all.zip, and the next gradle-1.12-all.zip is taken as an example. OK, we can modify the configuration:
distributionUrl=http\://services.gradle.org/distributions/gradle-2.1-all.zip
Then select
OK. Select import to add the module.
In the final analysis, the gradle compilation method is a bit similar to the Android Makefile method. In this way, the larger the project, the more obvious the advantage, but in our daily small app development, it seems a little bloated, and the compilation time is too long !!! I hope the official version can be improved and Google can do it.
The failure to import a project is caused by the fact that you are not familiar with the Gradle syntax and compiling environment. Therefore, it is very important to learn things and understand the principles, especially for something that has just begun to become popular, where there are so many ready-made things that can be used for your reference, you can only rely on yourself to Read The F ** king Source Code.
Above.