| commit | d90673afea7d6a01325d3026f88901573371a031 | [log] [tgz] |
|---|---|---|
| author | David Goldman <davg@google.com> | Wed Aug 09 17:46:09 2017 +0000 |
| committer | David Goldman <davg@google.com> | Wed Aug 09 20:55:56 2017 +0000 |
| tree | b7b0b14c35f03ed828d06ab4784b351600e7b9e4 | |
| parent | 3ae00753d89625bd961f6c9a198c2d75de509789 [diff] |
Bazel exec root relative FileReference paths Whenever Tulsi is unable to verify that a FileReference exists upon project generation, it will rewrite the path to be relative to Bazel's exec root. It will also exclude .xcassets that are not present as Xcode does not handle them properly. -- PiperOrigin-RevId: 164743811 MOS_MIGRATED_REVID=164743811
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.