xml - .xcscheme 文件中的 XML 元素有什么作用

Question

我正在创建一个 rake exe 以将覆盖范围添加到 xcode 项目。我正在使用 Gem xcodeproj。我需要创建一些版本控制方案并运行覆盖脚本。

我一直在构建自己的方案，但进展缓慢。我觉得如果我理解这些元素的含义，我就能更快地进行调试。

<?xml version="1.0" encoding="UTF-8"?>
   <Scheme
    LastUpgradeVersion = "0500"
  version = "1.3">
  <BuildAction
    parallelizeBuildables = "YES"
  buildImplicitDependencies = "YES">
     <BuildActionEntries>
     <BuildActionEntry
        buildForTesting = "YES"
        buildForRunning = "YES"
        buildForProfiling = "YES"
        buildForArchiving = "YES"
        buildForAnalyzing = "YES">
        <BuildableReference
           BuildableIdentifier = "primary"
           BlueprintIdentifier = "7B80F18918187FA5005578A0"
           BuildableName = "TestProj.app"
           BlueprintName = "TestProj"
           ReferencedContainer = "container:TestProj.xcodeproj">
        </BuildableReference>
     </BuildActionEntry>
  </BuildActionEntries>
  </BuildAction>
   <TestAction
  selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
  selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
  shouldUseLaunchSchemeArgsEnv = "YES"
  buildConfiguration = "Coverage">
  <Testables>
     <TestableReference
        skipped = "NO">
        <BuildableReference
           BuildableIdentifier = "primary"
           BlueprintIdentifier = "7B80F1A418187FA5005578A0"
           BuildableName = "TestProjTests.xctest"
           BlueprintName = "TestProjTests"
           ReferencedContainer = "container:TestProj.xcodeproj">
        </BuildableReference>
     </TestableReference>
      </Testables>
    <PostActions>
     <ExecutionAction
        ActionType =      "Xcode.IDEStandardExecutionActionsCore.ExecutionActionType.ShellScriptAction">
        <ActionContent
           title = "Run Script"
           scriptText = "/bin/sh ${SRCROOT}/bin/coverage.sh">
           <EnvironmentBuildable>
              <BuildableReference
                 BuildableIdentifier = "primary"
                 BlueprintIdentifier = "7B80F18918187FA5005578A0"
                 BuildableName = "TestProj.app"
                 BlueprintName = "TestProj"
                 ReferencedContainer = "container:TestProj.xcodeproj">
              </BuildableReference>
           </EnvironmentBuildable>
        </ActionContent>
     </ExecutionAction>
  </PostActions>
   </TestAction>
     <LaunchAction
  selectedDebuggerIdentifier = "Xcode.DebuggerFoundation.Debugger.LLDB"
  selectedLauncherIdentifier = "Xcode.DebuggerFoundation.Launcher.LLDB"
  launchStyle = "0"
  useCustomWorkingDirectory = "NO"
  buildConfiguration = "Debug"
  ignoresPersistentStateOnLaunch = "NO"
  debugDocumentVersioning = "YES"
  allowLocationSimulation = "YES">
  <AdditionalOptions>
  </AdditionalOptions>
  </LaunchAction>
    <ProfileAction
  shouldUseLaunchSchemeArgsEnv = "YES"
  savedToolIdentifier = ""
  useCustomWorkingDirectory = "NO"
  buildConfiguration = "Release"
  debugDocumentVersioning = "YES">
  </ProfileAction>
 <AnalyzeAction
    buildConfiguration = "Debug">
   </AnalyzeAction>
  <ArchiveAction
  buildConfiguration = "Release"
  revealArchiveInOrganizer = "YES">
    </ArchiveAction>
    </Scheme>

Answer 1

请注意，这只是非 iOS 开发人员的部分回答，因为我认为该问题符合 closing because of a lack of research 的要求。 :

回答所有这些值的含义会​​非常耗时，而且对于未参与您的项目的人来说是在浪费时间(尽管信息是公开的)。工程需要涉足文档和无休止的网站，以便在需要时回答哪怕是一小段信息。

Google 更独特的东西

下面的所有内容都是我在大约 15 分钟的谷歌搜索中能够完成的(当然，我将要引用的 Titolo 资源发布于 2015 年，您的问题发布于 2013 年):

由于我不是 iOS 开发人员，所以我无法确定这些类型资源的有效性；但是，它们似乎是合法的。我用 Google 搜索了 BlueprintIdentifier，因为它看起来很独特并且能够找到一些 good stuff on the second page of Google .

Michelle Titolo has done a good job of describing以下 XML 正文的目的(以及理解它所必需的术语):

<BuildActionEntry
    buildForTesting = ""
    buildForRunning = ""
    buildForProfiling = ""
    buildForArchiving = ""
    buildForAnalyzing = "">
    <BuildableReference
       BuildableIdentifier = ""
       BlueprintIdentifier = ""
       BuildableName = ""
       BlueprintName = ""
       ReferencedContainer = "">
    </BuildableReference>
 </BuildActionEntry>

其他的呢

@Antarr Byrd 早期在评论中发布的文档确实涵盖了这些内容。。例如，BuildableIdentifier 是 covered under the documentation对于 BuildableReference 节点也是 like LaunchAction .

我返回 Google 的次数越多，阅读的内容越多，我就越相信所有这些值(value)观都已被文档充分记录下来。它们可能不是预期的格式，但肯定已记录在案。

文档是人类编写的“东西”的结果。写这篇文章的人可能并不总是以易于理解的方式组织起来；但是，这并不意味着信息不存在。