SDK / ADT更新后破坏的Android Library依赖关系 [英] Android Library Dependencies broken after SDK/ADT-Update

问题描述

今天，我将Android SDK和Eciple ADT更新到最新版本（ADT Rev 22）。重新启动Eclipse之后，每当我引用自定义库时，它都对Build Paths感到不满。

Today, I updated my Android SDK and Eciple ADT to the most recent versions (ADT Rev 22). After restarting Eclipse it is quite unhappy with the Build Paths whenever I reference custom libraries.

此截图中显示了一个示例：

An example is shown in this screenshot:

我的自定义Android实用工具库编译好，但依赖于它的所有内容都会显示构建路径错误。例如。当我调查Android URA Library的构建路径设置时，它会显示Android依赖关系下的 android_utilities_library.jar 中的错误（实际上是这样，库将被构建到 bin / classes ）中的单个类文件。

My custom "Android Utilities Library" compiles fine, but everything that depends on it shows build path errors. E.g. when I investigate the build path settings for "Android URA Library" it shows me an error with the android_utilities_library.jar missing under "Android Dependencies" (which in fact is true, the libraries will be built to individual class files in bin/classes).

阅读使用库项目构建路径错误我试图以正确的顺序清理并手动构建我的项目，但没有用。

After reading the solution to Build path errors with library projects I tried to clean and manually build my projects in the correct order, but to no avail.

我以前从未处理过，所以我不知道如何攻击这个问题。

I've never dealt with this before, so I don't know how to attack the problem.

任何帮助不胜感激。 Thx！

Any help is appreciated. Thx!

推荐答案

安装新的Build Tools做了一个诀窍。当我更新SDK时，它们不会被自动添加（可能需要运行更新两次，我猜）。

Installing the new Build Tools did the trick. They were not automatically included when I updated the SDK (probably need to run the update twice I guess).

这篇关于SDK / ADT更新后破坏的Android Library依赖关系的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！