commit | 8af1ed4bc3920a9c5be80beb1e6395d2e4fc723d | [log] [tgz] |
---|---|---|
author | Nicholas Levin <nglevin@vivarium.gs> | Thu Jul 12 18:27:09 2018 -0400 |
committer | Jonathan Dierksen <dierksen@google.com> | Thu Jul 12 18:40:35 2018 -0400 |
tree | a02f6cc0eb8d3ec686c3e1ae1ee61f1b33e6ed91 | |
parent | 8fc7192c0244e315fa1d9123b52689e9879b9dee [diff] |
Print Bazel test errors to the Travis CI job log. In the current form which Travis CI is setup, the Bazel test errors are printed to a log file in its /private/var/... folder which is inaccessible after a test failure. See https://travis-ci.org/bazelbuild/tulsi/builds/397969960#L2063 for an example. Use of this flag will print all test errors to the console instead, making them visible in Travis CI's job log. Closes #54. PiperOrigin-RevId: 204375657
Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.
Run the TulsiApp.
Tulsi-generated Xcode projects use Bazel to build, not Xcode via xcbuild. This means that many common components of an Xcode project are handled differently than you may be used to. Notable differences: