commit | 0a8a12d6328a8d4a0e7d68062e5f4668f180b5f5 | [log] [tgz] |
---|---|---|
author | Dmitry Shevchenko <dmishe@google.com> | Wed Jun 21 17:39:46 2017 +0000 |
committer | Sergio Campamá <kaipi@google.com> | Wed Jun 21 18:35:51 2017 +0000 |
tree | 7243ce0c016fd9046f5f64d08b8049a96265c342 | |
parent | daa35466c84331473af3d776f8cd365dd284ce7a [diff] |
Use Bazel repos for Tulsi scripts * Bazel's new --override_repository flag allows us to reference Tulsi repo on disk without overriding --package_path. It simplifies Tulsi's package handling, and fixes the issue with spurious rebuilds when package_path changes between bazel invocations. -- PiperOrigin-RevId: 159711377 MOS_MIGRATED_REVID=159711377
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.