commit | 994918b4b93335921f1355b96a6cb532e10436b6 | [log] [tgz] |
---|---|---|
author | hlopko <hlopko@google.com> | Fri Oct 19 04:23:44 2018 -0400 |
committer | Rein Hillmann <rein@google.com> | Wed Oct 24 15:30:18 2018 -0400 |
tree | fcae6d8e9f34df19d0466531f0eb7bc1fbe7eaaa | |
parent | 19e8b557e79747773aecd425acc575cefeaadedb [diff] |
Migrate users of C++ toolchain API for --incompatible_disable_depset_in_cc_user_flags This is a migration needed do move g3 forward so unknown commit can be submitted, and in case of Bazel users, to make them forward compatible with Bazel 0.20. Migration details and discussion are over at github: https://github.com/bazelbuild/bazel/issues/6383 PiperOrigin-RevId: 217837227
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.