XCode 4“清洁”与“清洁构建文件夹”相对 [英] XCode 4 "Clean" vs. "Clean Build Folder"

问题描述

在每个应用程序的开发过程中，您在模拟器中看到的内容与您认为应该发生的内容不匹配。大多数情况下这些是人为错误 - 或者至少它们属于我的案例中的大多数情况;-) - 但有时Xcode只是失去了轨道，或者看起来如此。我已经知道 Clean （Shift + Cmd + K）和 Clean Build Folder ... （Option + Shift + Command + K）菜单选项可以显示错误或Xcode之间的差异。

You come at a certain point in the development of every app that what you see in the simulator does not match what you think should happen. Mostly these are human errors -- or at least they are in most of my cases ;-) -- but sometimes Xcode has just 'lost track', or so it seems. I've learnt that the Clean (Shift+Cmd+K) and Clean Build Folder… (Option+Shift+Command+K) menu options can show the difference between your error or Xcode's.

我的问题是：

干净命令做或不做，这留下了清理构建文件夹... 存在的原因？我何时应该选择其中一个，为什么不总是清理整个文件夹？

What does the Clean command do or not do, which leaves a reason for Clean Build Folder… to exist? When should I pick one over the other, why not just always clean the whole folder?

推荐答案

清理... 清除当前所选目标的文件夹。

清理构建文件夹... 清除所有目标的文件夹。

Clean… cleans the folders for the current selected target.
Clean Build Folder… cleans the folders for all the targets.

这篇关于XCode 4“清洁”与“清洁构建文件夹”相对的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！