commit | d0e538fb8bfa865e4f3fe77c813779060700de65 | [log] [tgz] |
---|---|---|
author | davg <davg@google.com> | Fri Feb 09 11:07:31 2018 -0800 |
committer | Nicholas <nglevin@google.com> | Wed Feb 14 13:03:34 2018 -0800 |
tree | bcce341010f5274ce2c03c78b54f50c45cd0fa06 | |
parent | 578eb4788b90aea576785ec9dc7d985315aad291 [diff] |
Rename tulsi-workspace to _tulsi-workspace This prevents Bazel from removing the folder whenever it builds. Bazel removing the folder when it builds causes issues whenever a build fails, as tulsi-includes will disappear which causes Xcode to lose indexing and auto-completion for generated files and artifacts. See SymlinkForest.java for more information in how Bazel clears folders in the exec root before building. PiperOrigin-RevId: 185165612
Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.
Run the TulsiApp.
Tulsi-generated Xcode projects use Bazel to build, not Xcode via xcbuild. This means that many common components of an Xcode project are handled differently than you may be used to. Notable differences: