commit | af3b223fe056c722e202eae5cc1e5e0e1e938771 | [log] [tgz] |
---|---|---|
author | Dmitry Shevchenko <dmishe@google.com> | Tue Dec 12 00:53:11 2017 +0000 |
committer | Dmitry Shevchenko <dmishe@google.com> | Wed Dec 13 18:34:47 2017 +0000 |
tree | 44e23de8eaa15322cbfa1f715e7d20f7c2bf8ea2 | |
parent | b0e82054dbf3bc5734a2d79c92c8d79d2a0045ff [diff] |
Add an option to skip adding Skylark files By default Tulsi will try to add Skylark sources (.bzl) to the generated project for user convenience. In order to do this, Tulsi runs a "bazel query" command which can take a really long time on big build graphs. This change adds a project-level flag that when set, will tell Tulsi to skip Skylark sources, avoid using the query, improving the project gen time. -- PiperOrigin-RevId: 178694348 MOS_MIGRATED_REVID=178694348
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.