commit | 4eefc3dc65eb3e919139cacbb54cd834b5b2d5e4 | [log] [tgz] |
---|---|---|
author | Nicholas Levin <nglevin@google.com> | Thu Nov 16 19:32:11 2017 +0000 |
committer | Nicholas Levin <nglevin@google.com> | Thu Nov 30 19:41:01 2017 +0000 |
tree | 9d9261dba478aa42ece3a3f11e2a8a267fa2a170 | |
parent | aa50be411d6e0277a9e4bdfcd0a7705a0921c028 [diff] |
Add file lock to serialize bazel_build.py builds. This serializes not only the Bazel build invocations, but also the Tulsi script actions to delete symlinks, clear temp files, remove assumed expired dSYMs, and others to prevent accidentally parallel behavior. -- PiperOrigin-RevId: 175993048 MOS_MIGRATED_REVID=175993048
Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.
Run the TulsiApp.
Tulsi-generated Xcode projects use Bazel to build, rather than Xcode. This means that many common components of an Xcode project are handled differently than you may be used to. For example, the Info.plist file is governed entirely by BUILD rules in Bazel and is not displayed in the Xcode UI. It also means that changes made to your BUILD files, such as adding new library dependencies, are incorporated automatically when building your generated project. The only time you need to re-run Tulsi is if you want to add additional build targets or have new source files show up in Xcode for editing.