commit | de5efc7d391714146ace93d00d23eb2f01bd625c | [log] [tgz] |
---|---|---|
author | davg <davg@google.com> | Mon Jul 16 16:27:46 2018 -0400 |
committer | Jonathan Dierksen <dierksen@google.com> | Wed Jul 18 19:43:12 2018 -0400 |
tree | dc4a2120ad384611da524240629ca1d882fbf212 | |
parent | 2dc68d19b721b9be17777bd134a59dc570c39c5b [diff] |
Add Bazel feature flags functionality This allows Tulsi to define flags conditional on Swift/non-Swift, certain project configurations, etc. without impacting the Bazel analysis cache. Previously we would directly set Build Settings on the generated xcodeproj in order to pass down these flags; however, this is not a valid solution for caching reasons. PiperOrigin-RevId: 204796507
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: