commit | d7a8704de01b8bb874e9b325b68c398631195a39 | [log] [tgz] |
---|---|---|
author | David Goldman <davg@google.com> | Tue Dec 12 22:25:10 2017 +0000 |
committer | Dmitry Shevchenko <dmishe@google.com> | Wed Dec 13 18:35:28 2017 +0000 |
tree | 7adc218b1dc6505cab49577eda3057403d669bd6 | |
parent | cab06bf0f47a920785f11aca8ef22f8475b0a22f [diff] |
Fix issue related to Swift tests Our test targets with Swift code contain special run scripts which creates files in the places where Xcode expects them. The scripts did not use the right ENV vars, so in rare cases they could create the wrong files, leading to errors during build time. -- PiperOrigin-RevId: 178814845 MOS_MIGRATED_REVID=178814845
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.