commit | 3bf662cc0702d30577ef30e0fd9e2effcd877e29 | [log] [tgz] |
---|---|---|
author | davg <davg@google.com> | Wed Aug 22 18:11:18 2018 -0400 |
committer | David Goldman <davg@google.com> | Thu Aug 23 12:47:02 2018 -0400 |
tree | 5f3157728c2118654e6b4002507022a6437d293a | |
parent | 17d088b50b4800b2cbeeedffe589787541a6e0d4 [diff] |
Improve handling of Swift tests Tulsi needs to make sure that it doesn't include the modulemap file for any direct dependencies of the test targt as it may conflict with the source files that are added to the Test Target in Xcode. PiperOrigin-RevId: 209838173
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:
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.