当前位置:   article > 正文

Android Studio的安装详细步骤_android studio安装教程

android studio安装教程

Android Studio的安装需要使用到Gradle,JDK,甚至是maven

目录

安装的第一步:

第二步  安装gradle(最好对应Android studio的gradle版本)

 第三步 安装Android Studio

 第四步 随便创建一个 有activity的项目(路径没有中文)


安装的第一步:

卸载原有的Android Studio

如上图所示的步骤卸载原来的 Android Studio,还原原来的安装模式

第二步  安装gradle(最好对应Android studio的gradle版本)

国内镜像地址腾讯仓库https://mirrors.cloud.tencent.com/gradle/

下载解压后

放到路径无中文的任何位置

配置环境变量

 GRADLE_PATH

复制这路径 

添加到

 

 

 

此时还没有.gradle

 进入dom窗口

相当于初始化gradle 

 添加初始化脚本(全局使用的),为了解决由于gradle的下载以及访问外网的速度,实际上就是使用国内镜像网站下载资源,因为国内因素访问外网都是很慢的。这导致很多人安装都会失败。

init.gradle

  1. allprojects {
  2. buildscript {
  3. repositories {
  4. maven { url 'https://maven.aliyun.com/repository/public/' }
  5. maven { url 'https://maven.aliyun.com/repository/google/' }
  6. }
  7. }
  8. repositories {
  9. maven { url 'https://maven.aliyun.com/repository/public/' }
  10. maven { url 'https://maven.aliyun.com/repository/google/' }
  11. }
  12. println "${it.name}: Aliyun maven mirror injected"
  13. }

第三步  配置好之前的idea

你会发现 idea默认配置maven的配置文件在这里 

 

这里是因为我之前就配置好了,没有的话

自己自行配置

这里主要配置本地仓库 以及 maven包的下载地址<localRepository>(科学上网除外),使用国内镜像<mirrors>

 

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!--
  3. Licensed to the Apache Software Foundation (ASF) under one
  4. or more contributor license agreements. See the NOTICE file
  5. distributed with this work for additional information
  6. regarding copyright ownership. The ASF licenses this file
  7. to you under the Apache License, Version 2.0 (the
  8. "License"); you may not use this file except in compliance
  9. with the License. You may obtain a copy of the License at
  10. http://www.apache.org/licenses/LICENSE-2.0
  11. Unless required by applicable law or agreed to in writing,
  12. software distributed under the License is distributed on an
  13. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  14. KIND, either express or implied. See the License for the
  15. specific language governing permissions and limitations
  16. under the License.
  17. -->
  18. <!--
  19. | This is the configuration file for Maven. It can be specified at two levels:
  20. |
  21. | 1. User Level. This settings.xml file provides configuration for a single user,
  22. | and is normally provided in ${user.home}/.m2/settings.xml.
  23. |
  24. | NOTE: This location can be overridden with the CLI option:
  25. |
  26. | -s /path/to/user/settings.xml
  27. |
  28. | 2. Global Level. This settings.xml file provides configuration for all Maven
  29. | users on a machine (assuming they're all using the same Maven
  30. | installation). It's normally provided in
  31. | ${maven.conf}/settings.xml.
  32. |
  33. | NOTE: This location can be overridden with the CLI option:
  34. |
  35. | -gs /path/to/global/settings.xml
  36. |
  37. | The sections in this sample file are intended to give you a running start at
  38. | getting the most out of your Maven installation. Where appropriate, the default
  39. | values (values used when the setting is not specified) are provided.
  40. |
  41. |-->
  42. <settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
  43. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  44. xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">
  45. <!-- localRepository
  46. | The path to the local repository maven will use to store artifacts.
  47. |
  48. | Default: ${user.home}/.m2/repository
  49. -->
  50. <localRepository>H:\apache-maven-3.8.6-bin\apache-maven-3.8.6\localRepository</localRepository>
  51. <!-- interactiveMode
  52. | This will determine whether maven prompts you when it needs input. If set to false,
  53. | maven will use a sensible default value, perhaps based on some other setting, for
  54. | the parameter in question.
  55. |
  56. | Default: true
  57. <interactiveMode>true</interactiveMode>
  58. -->
  59. <!-- offline
  60. | Determines whether maven should attempt to connect to the network when executing a build.
  61. | This will have an effect on artifact downloads, artifact deployment, and others.
  62. |
  63. | Default: false
  64. <offline>false</offline>
  65. -->
  66. <!-- pluginGroups
  67. | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
  68. | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
  69. | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
  70. |-->
  71. <pluginGroups>
  72. <!-- pluginGroup
  73. | Specifies a further group identifier to use for plugin lookup.
  74. <pluginGroup>com.your.plugins</pluginGroup>
  75. -->
  76. </pluginGroups>
  77. <!-- proxies
  78. | This is a list of proxies which can be used on this machine to connect to the network.
  79. | Unless otherwise specified (by system property or command-line switch), the first proxy
  80. | specification in this list marked as active will be used.
  81. |-->
  82. <proxies>
  83. <!-- proxy
  84. | Specification for one proxy, to be used in connecting to the network.
  85. |
  86. <proxy>
  87. <id>optional</id>
  88. <active>true</active>
  89. <protocol>http</protocol>
  90. <username>proxyuser</username>
  91. <password>proxypass</password>
  92. <host>proxy.host.net</host>
  93. <port>80</port>
  94. <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
  95. </proxy>
  96. -->
  97. </proxies>
  98. <!-- servers
  99. | This is a list of authentication profiles, keyed by the server-id used within the system.
  100. | Authentication profiles can be used whenever maven must make a connection to a remote server.
  101. |-->
  102. <servers>
  103. <!-- server
  104. | Specifies the authentication information to use when connecting to a particular server, identified by
  105. | a unique name within the system (referred to by the 'id' attribute below).
  106. |
  107. | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
  108. | used together.
  109. |
  110. <server>
  111. <id>deploymentRepo</id>
  112. <username>repouser</username>
  113. <password>repopwd</password>
  114. </server>
  115. -->
  116. <!-- Another sample, using keys to authenticate.
  117. <server>
  118. <id>siteServer</id>
  119. <privateKey>/path/to/private/key</privateKey>
  120. <passphrase>optional; leave empty if not used.</passphrase>
  121. </server>
  122. -->
  123. </servers>
  124. <!-- mirrors
  125. | This is a list of mirrors to be used in downloading artifacts from remote repositories.
  126. |
  127. | It works like this: a POM may declare a repository to use in resolving certain artifacts.
  128. | However, this repository may have problems with heavy traffic at times, so people have mirrored
  129. | it to several places.
  130. |
  131. | That repository definition will have a unique id, so we can create a mirror reference for that
  132. | repository, to be used as an alternate download site. The mirror site will be the preferred
  133. | server for that repository.
  134. |-->
  135. <!-- 阿里云仓库 -->
  136. <mirrors>
  137. <mirror>
  138. <id>alimaven</id>
  139. <name>aliyun maven</name>
  140. <mirrorOf>central</mirrorOf>
  141. <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
  142. </mirror>
  143. <!-- 中央仓库1 -->
  144. <mirror>
  145. <id>repo1</id>
  146. <mirrorOf>central</mirrorOf>
  147. <name>Human Readable Name for this Mirror.</name>
  148. <url>http://repo1.maven.org/maven2/</url>
  149. </mirror>
  150. <!-- 中央仓库2 -->
  151. <mirror>
  152. <id>repo2</id>
  153. <mirrorOf>central</mirrorOf>
  154. <name>Human Readable Name for this Mirror.</name>
  155. <url>http://repo2.maven.org/maven2/</url>
  156. </mirror>
  157. <!-- mirror
  158. | Specifies a repository mirror site to use instead of a given repository. The repository that
  159. | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
  160. | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
  161. |
  162. <mirror>
  163. <id>mirrorId</id>
  164. <mirrorOf>repositoryId</mirrorOf>
  165. <name>Human Readable Name for this Mirror.</name>
  166. <url>http://my.repository.com/repo/path</url>
  167. </mirror>
  168. -->
  169. <!-- <mirror>
  170. <id>maven-default-http-blocker</id>
  171. <mirrorOf>external:http:*</mirrorOf>
  172. <name>Pseudo repository to mirror external repositories initially using HTTP.</name>
  173. <url>http://0.0.0.0/</url>
  174. <blocked>true</blocked>
  175. </mirror> -->
  176. </mirrors>
  177. <!-- profiles
  178. | This is a list of profiles which can be activated in a variety of ways, and which can modify
  179. | the build process. Profiles provided in the settings.xml are intended to provide local machine-
  180. | specific paths and repository locations which allow the build to work in the local environment.
  181. |
  182. | For example, if you have an integration testing plugin - like cactus - that needs to know where
  183. | your Tomcat instance is installed, you can provide a variable here such that the variable is
  184. | dereferenced during the build process to configure the cactus plugin.
  185. |
  186. | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
  187. | section of this document (settings.xml) - will be discussed later. Another way essentially
  188. | relies on the detection of a system property, either matching a particular value for the property,
  189. | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
  190. | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
  191. | Finally, the list of active profiles can be specified directly from the command line.
  192. |
  193. | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
  194. | repositories, plugin repositories, and free-form properties to be used as configuration
  195. | variables for plugins in the POM.
  196. |
  197. |-->
  198. <profiles>
  199. <!-- profile
  200. | Specifies a set of introductions to the build process, to be activated using one or more of the
  201. | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
  202. | or the command line, profiles have to have an ID that is unique.
  203. |
  204. | An encouraged best practice for profile identification is to use a consistent naming convention
  205. | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
  206. | This will make it more intuitive to understand what the set of introduced profiles is attempting
  207. | to accomplish, particularly when you only have a list of profile id's for debug.
  208. |
  209. | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
  210. <profile>
  211. <id>jdk-1.4</id>
  212. <activation>
  213. <jdk>1.4</jdk>
  214. </activation>
  215. <repositories>
  216. <repository>
  217. <id>jdk14</id>
  218. <name>Repository for JDK 1.4 builds</name>
  219. <url>http://www.myhost.com/maven/jdk14</url>
  220. <layout>default</layout>
  221. <snapshotPolicy>always</snapshotPolicy>
  222. </repository>
  223. </repositories>
  224. </profile>
  225. -->
  226. <!--
  227. | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
  228. | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
  229. | might hypothetically look like:
  230. |
  231. | ...
  232. | <plugin>
  233. | <groupId>org.myco.myplugins</groupId>
  234. | <artifactId>myplugin</artifactId>
  235. |
  236. | <configuration>
  237. | <tomcatLocation>${tomcatPath}</tomcatLocation>
  238. | </configuration>
  239. | </plugin>
  240. | ...
  241. |
  242. | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
  243. | anything, you could just leave off the <value/> inside the activation-property.
  244. |
  245. <profile>
  246. <id>env-dev</id>
  247. <activation>
  248. <property>
  249. <name>target-env</name>
  250. <value>dev</value>
  251. </property>
  252. </activation>
  253. <properties>
  254. <tomcatPath>/path/to/tomcat/instance</tomcatPath>
  255. </properties>
  256. </profile>
  257. -->
  258. </profiles>
  259. <!-- activeProfiles
  260. | List of profiles that are active for all builds.
  261. |
  262. <activeProfiles>
  263. <activeProfile>alwaysActiveProfile</activeProfile>
  264. <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  265. </activeProfiles>
  266. -->
  267. </settings>

这里有些细节 可以自寻maven的配置

 第四步 安装Android Studio

首先访问

Download Android Studio & App Tools - Android Developers

这是Android Studio的国内官方下载地址

下载完成后

安装

 

 

 

 

这里是我的jdk的放置位置

 

这里由于我之前已经下好了sdk的缘故,如果没有sdk的话,需要放置到路径没有中文的文件夹下 

 

需要接受的都得接受

等待下载完成后(大约1小时) 

 

 

 第四步 随便创建一个 有activity的项目(路径没有中文)

gradle开始下载 资源

 

 这里会出现下载中断报错的原因

这里就需要重新构建

也就是重新下载资源

这里你会发现使用的是阿里云的仓库下载资源

所有资源下载完成

这里可以选择usb连接手机或者虚拟手机使用 

 这里是运行成功的效果

声明:本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有侵权的内容,请联系我们。转载请注明出处:【wpsshop博客】
推荐阅读
相关标签
  

闽ICP备14008679号