| commit | b24c6b3400bab483642f46bc81f792333f8659f5 | [log] [tgz] |
|---|---|---|
| author | Dmitry Shevchenko <dmishe@google.com> | Mon Oct 16 23:45:56 2017 +0000 |
| committer | David Goldman <davg@google.com> | Thu Oct 19 20:19:25 2017 +0000 |
| tree | 12ad5777b78e7e5e69ee683332de47dfaa998dc6 | |
| parent | 88d7a4fbf1a0349ba5d7a225d637214d50ac2403 [diff] |
Add dSYM from deps of a target This feature, covered by a settings flag, will let Tulsi collect and process additional dSYM bundles coming from extensions or frameworks of a target being built. -- PiperOrigin-RevId: 172398569 MOS_MIGRATED_REVID=172398569
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.