commit | 3423e56f7dda31a65b4c72872c2ea4a82a413939 | [log] [tgz] |
---|---|---|
author | David Goldman <davg@google.com> | Tue Oct 10 20:15:17 2017 +0000 |
committer | David Goldman <davg@google.com> | Thu Oct 12 22:06:50 2017 +0000 |
tree | 9eb11ab793ad8b2b7e495d09e3adf7419dfa227e | |
parent | 8547a3ec8da8500d2da40a5a06c954b8558bbcfc [diff] |
Fix version group path handling XCVersionGroup's paths should behave exactly like PBXGroup's paths, meaning the groups should not contain path information while the file references should contain all path information relative to the main group. -- PiperOrigin-RevId: 171723584 MOS_MIGRATED_REVID=171723584
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.