| commit | 33580c94f28b8161be1b7851736d38e20d3dea3a | [log] [tgz] |
|---|---|---|
| author | David Goldman <davg@google.com> | Mon Oct 09 15:06:15 2017 +0000 |
| committer | David Goldman <davg@google.com> | Thu Oct 12 22:05:50 2017 +0000 |
| tree | ca30ac4fc48f81f7b26436c9c91b7be97d141a0d | |
| parent | c270823f94df5ab2f08d8b8cdf990f8eec8839f5 [diff] |
Use a set when collecting tulsiinfo artifacts On certain projects, artifact paths will be outputted multiple times when building. Previously this would lead to duplicated RuleEntries when parsing, which was okay when overriden by the same file. -- PiperOrigin-RevId: 171536054 MOS_MIGRATED_REVID=171536054
Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.
Run the TulsiApp.
Tulsi-generated Xcode projects use Bazel to build, rather than Xcode. This means that many common components of an Xcode project are handled differently than you may be used to. For example, the Info.plist file is governed entirely by BUILD rules in Bazel and is not displayed in the Xcode UI. It also means that changes made to your BUILD files, such as adding new library dependencies, are incorporated automatically when building your generated project. The only time you need to re-run Tulsi is if you want to add additional build targets or have new source files show up in Xcode for editing.