| commit | db0df1ada16f144ac826f663b6c85b7305d217ba | [log] [tgz] |
|---|---|---|
| author | Dmitry Shevchenko <dmishe@google.com> | Thu Mar 16 15:17:11 2017 +0000 |
| committer | Kelvin Chan <kelvinchan@google.com> | Fri Mar 17 18:50:13 2017 +0000 |
| tree | 5c433658caae97004821a6d81ee3ed97cca0e2e8 | |
| parent | c27ce490f072a32be1d5848d73e94a679eb5fd46 [diff] |
Add an aspect to collect build outputs. * WORKSPACE file and the "tulsi" package is now copied into the generated Xcode project. This ensures that the aspect can be used on every bazel_build.py invocation. * The new aspect is disabled by default and is used for development purposes. -- PiperOrigin-RevId: 150321088 MOS_MIGRATED_REVID=150321088
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.