commit | fbe84aededbc1bd6ce5eecafefab33ddc3e27dc3 | [log] [tgz] |
---|---|---|
author | dierksen <dierksen@google.com> | Fri Jan 18 16:38:22 2019 -0500 |
committer | David Goldman <davg@google.com> | Wed Jan 23 17:08:09 2019 -0500 |
tree | 50562b3abb93a2a292950385f7209f3b1815947e | |
parent | efb05dfd80a5a6c019003983e8f31f3287d8cdf5 [diff] |
Move BUILD file for tulsi_aspects to top-level rather than one level down. This makes it easier to reference the aspect via Tulsi and directly without having to change the load paths. This also makes it possible to use the vscode-bazel debugger to debug the Tulsi aspect. PiperOrigin-RevId: 229985479
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.