Android的SDK构建，工具，错误或多个实例？ [英] Multiple instances of Android SDK Build-Tools, Bug or Feature?

问题描述

在过去的几个月我已经注意到一个奇怪的行为在Android SDK管理器。最近推出的 Android SDK中内建工具的似乎并没有得到的更新而是被认为是单独的包

For the last couple of months I've been noticing a strange behaviour in the Android SDK Manager. The recently introduced Android SDK Build-Tools don't seem to get updated but instead are recognised as separate packages

在一直增加和种类它扰乱了我。现在，每当我看到一个新的包我求助于刚刚卸载旧版本并安装新的，因为我认为会有版本冲突，如果我安装一个软件包的多个实例

The list keeps growing and it kind of disturbs me. Now whenever I see a new package I resort to just uninstalling the older version and installing the new one because I suspect there might be version conflicts if I have multiple instances of the same package installed

奇怪的是，这种行为是通过我的系统上的每个SDK管理器shwon（我有多个ADT安装使用），所以我问自己：

Oddly enough, this behaviour is shwon by every SDK Manager on my system (I have multiple ADT installations in use) and so I ask myself:

也许这是故意的？如果是的话：什么是它背后的原因

我会很乐意接受，如果是这样，但是当我在寻找这个问题的interwebs所有我似乎可以找到截图的预期行为：一是包被替换更新时（如 Android的SDK工具的为例）。我至今没有能够找到一个单线程/博客/帖子里有人抱怨这个

I would gladly accept that if it is so, but when I was searching for this issue on the interwebs all I can seem to find in screenshots is the expected behaviour: one package that gets replaced when it is updated (like the Android SDK Tools for example). I have so far not been able to find one single thread/blog/post where someone complains about this

推荐答案

原因很简单

如果有人需要下载旧版本   兼容的目的

"What if someone requires to download the older version for compatibility purposes"

如果在ADT覆盖的每个新修订或版本到软件的条目，用户将不能够下载早期版本，因为它们是在工具，而不是作为单独的版本，如的API的SDK一起分组

If the ADT overwrites the entry for every new revision or version to the software, user won't be able to download the earlier version because they are together grouped under "Tools" and not as separate versions as in "API SDK"

这篇关于Android的SDK构建，工具，错误或多个实例？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！