commit | 005437c679dbb6da52923285a0014da8473be778 | [log] [tgz] |
---|---|---|
author | davg <davg@google.com> | Thu Apr 05 13:39:15 2018 -0400 |
committer | kelvinchan-google <kelvinchan@google.com> | Thu Apr 05 17:44:04 2018 -0400 |
tree | 7583b50fa967f35591f379951364b8854dc5b60e | |
parent | 278ecf71dafbe2e0c9b7ad7446a905d27e895c5a [diff] |
Don't set the -fmodule-map-file args for indexers Otherwise, the flag will break on swift targets which contain their own swift module map. Note that Xcode currently only uses the last -fmodule-map-file arg passed for indexing, making the flag not particularly useful at the moment. Testing shows that just including the containing directory seems to be enough for Xcode to properly parse the modulemap. In the future, once Xcode properly supports the flag with indexing, we should have Tulsi ignore the swift's target module map. PiperOrigin-RevId: 191762697
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: