commit | b0e82054dbf3bc5734a2d79c92c8d79d2a0045ff | [log] [tgz] |
---|---|---|
author | Sergio Campamá <kaipi@google.com> | Mon Dec 11 22:57:12 2017 +0000 |
committer | Dmitry Shevchenko <dmishe@google.com> | Wed Dec 13 18:34:42 2017 +0000 |
tree | 3212ed917b4354220b8ffd831da9a8b29543df93 | |
parent | 3402287bd99c714b7841e7d62c85daefd0841e5b [diff] |
Disable propagation of non embeddable bundles. This change disables the test_host attribute from propagating its dependency as an embedded bundle. In bazel, tests depend on their test host, but from Xcode perspective, test hosts contain the embedded bundle. This fixes an issue where Tulsi would overwrite the test host after the tests were unpacked inside of it, when running tests for macOS.. -- PiperOrigin-RevId: 178678081 MOS_MIGRATED_REVID=178678081
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.