commit | 4d7e0c1e5ed16d8ec32a92d2484407063f9d0b29 | [log] [tgz] |
---|---|---|
author | davg <davg@google.com> | Wed May 16 14:43:57 2018 -0400 |
committer | David Goldman <davg@google.com> | Wed May 16 18:40:42 2018 -0400 |
tree | 8a2950e6d6aaf2574938a39de7f899055f25e345 | |
parent | 750dc7d4eddf691117cebf815e163a4d10af39cb [diff] |
Improve Swift indexing of generated ObjC code Regression was caused by https://github.com/bazelbuild/tulsi/commit/005437c679dbb6da52923285a0014da8473be778. Without the '-Xcc -fmodule-map-file=<>' flag, Xcode's indexing breaks for generated Objective-C code being used in Swift. PiperOrigin-RevId: 196863234
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: