commit | c553f66470ae683f9fbcef46aacd99c147ecbd40 | [log] [tgz] |
---|---|---|
author | nglevin <nglevin@google.com> | Mon Jan 22 12:27:18 2018 -0500 |
committer | David Goldman <davg@google.com> | Mon Jan 22 18:27:07 2018 -0500 |
tree | 9b388654ad2385497ea43f1146e5e06541fbfe50 | |
parent | e5aa76927ab939a5d2b29d829f1a19dc2a5ce1fd [diff] |
Workaround for saving tulsigen configs. This is based on NSDocument's header file documentation, which states that this write method is called within writeSafely after making sure through NSFileCoordinator (itself a limited means of locking) that it is safe to read or write to a temporary directory for atomic writing of document data. That's not really necessary for Configs, to be honest. PiperOrigin-RevId: 182790128
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: