commit | 57d464c33e3724392ab8ffc67f25881a05fbabda | [log] [tgz] |
---|---|---|
author | nglevin <nglevin@google.com> | Tue Jan 23 17:51:19 2018 -0500 |
committer | Jonathan Dierksen <dierksen@google.com> | Wed Jan 24 19:37:33 2018 -0500 |
tree | c279c40ec61f9ccf8daeaf0b6a16ce403866e5d7 | |
parent | b014253ea5eaf46f032de2615d3d156e731ad14c [diff] |
Resolve issue refreshing Tulsi Project. When adding a new config, the Tulsi Project document was not directly informed of the new config changes. Now, we pass along the name of the new Tulsi config document to keep the Tulsi project document up to date. PiperOrigin-RevId: 182996722
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: