| commit | 1f5ca402f979bd5f50f924100871535d890352f7 | [log] [tgz] |
|---|---|---|
| author | Nicholas Levin <nglevin@google.com> | Mon Sep 11 22:52:59 2017 +0000 |
| committer | David Goldman <davg@google.com> | Wed Sep 13 22:12:00 2017 +0000 |
| tree | a3cc5e3ac58f64e2826e09173c96715c959b183b | |
| parent | c5a7b74d0fadf0959b7f408ad027cee58219f2c3 [diff] |
Clean up exception error messaging. Removed the duplicated errors and reduced messaging to the source of the exception, avoid repeating what has already been Syslogged. -- PiperOrigin-RevId: 168298654 MOS_MIGRATED_REVID=168298654
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.