commit | efa3daceb6f45571aef2ccf1d3a683a3040a62b7 | [log] [tgz] |
---|---|---|
author | ivanhernandez <ivanhernandez@google.com> | Tue Feb 12 13:45:51 2019 -0500 |
committer | Jonathan Dierksen <dierksen@google.com> | Tue Feb 12 14:41:33 2019 -0500 |
tree | c997aee8896755b4ccc9c2818b335f89d0566244 | |
parent | e4a568c02f28d4c5190d380c74584615d36f002a [diff] |
Adds a step to preboot a simulator before attempting to run a test on it. Also bumps the simulator to an 'iPhone XS' running iOS 12.1. Also made changes to ensure each test case is hermetic. A fresh simulator is created before any tests are run and deleted after all tests have completed. The simulator is booted and launched before each test case and is shutdown and wiped after each test case. PiperOrigin-RevId: 233635794
build_and_run.sh
. This will install Tulsi.app inside ~/Applications.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:
bazel
invocations, some of which may affect Bazel caching. In order to maximize cache re-use when building from the command line, try using the user_build.py
script which is located in the generated xcodeproj at <xcodeproj>/.tulsi/Scripts/user_build.py
.Tulsi projects contain a few settings which control various behaviors during project generation and builds.
build
flags, customizable per compilation mode (dbg
and opt
)build
startup flags, also customizable per compilation modedbg
or opt
, no fastbuild
) used during project generation.dbg
, swap to opt
if you normally build Release builds in Xcode (i.e. profiling your app). Setting this improperly shouldn't break your project although it may potentially worsen generation and build performance.No
, swap to Yes
if your project contains Swift (even in its dependencies). Setting this improperly shouldn't break your project although it may potentially worsen generation and build performance.