清洁机制项目的Andr​​oid [英] clean project Mechanism Android

问题描述

有什么优势或魔法或mechanisum背后清洁工程？

一段时间，我们实现了code未在最终的输出效果，我们是干净的（：来自：项目资源管理器＆GT;＆GT;清洁：）并按预期产出均在us.some时间R.java也用不了资源前，当我们清理它去正确的方式。

何洁是建设？不同

所以现在我想知道它背后机制。

解决方案

  

何洁是建设有什么不同？

清洁项目摆脱已编译的类，迫使所有类的完全重新编译。

在Android开发，这有时会清除了其中 R.java 生成的类获取与新的资源ID重新编译出了问题，而是previously编译的类（其中，从研发的各个数字常量的字节code得到内联）没有得到重新编译，以反映相同的更改。

what is advantage or magic or mechanisum behind clean project?

some time we implement code which are not effect in final output and we are clean (: from: project Explorer >> clean :) it and as per expected output are in front of us.some time R.java are also not take resource and as we clean it it going to right way.

how clean is different from buildup ?

so now i would like to know Mechanism behind it.

解决方案

how clean is different from buildup ?

Cleaning a project gets rid of already-compiled classes, forcing a full recompile of all of your classes.

In Android development, this sometimes clears up a problem where the R.java generated class gets recompiled with new resource IDs, but the previously-compiled classes (where the various numeric constants from R get inlined in the bytecode) do not get recompiled to reflect the same changes.

这篇关于清洁机制项目的Andr​​oid的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！