| commit | 2d8b66a98b87145c5e6be5f6b8157845384e39b2 | [log] [tgz] |
|---|---|---|
| author | David Goldman <davg@google.com> | Tue Dec 05 22:28:07 2017 +0000 |
| committer | David Goldman <davg@google.com> | Wed Dec 06 20:46:43 2017 +0000 |
| tree | 37bf8fbcd29d1ff95b1855ae4df6d8257a2ee03f | |
| parent | 4a3507c6c63fd95809846ff53af82e379398859a [diff] |
Set include paths for Xcode test targets This should improve indexing in Xcode test targets. Note that having the test sources added to the test targets themselves is a hack and thus we don't expect this to be working perfectly. Specifically, we don't respect the defines nor copts as we'd have to scope them per file. -- PiperOrigin-RevId: 178011515 MOS_MIGRATED_REVID=178011515
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.