|author||davg <email@example.com>||Wed Aug 21 11:33:56 2019 -0400|
|committer||Rein Hillmann <firstname.lastname@example.org>||Thu Aug 22 20:54:31 2019 -0400|
Move _tulsi-includes -> bazel-tulsi-includes This will prevent Bazel from removing the directory as Bazel no longer preserves directories starting with _. This will fix some indexing issues, especially after build failure. PiperOrigin-RevId: 264614781
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:
bazelinvocations, 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.pyscript which is located in the generated xcodeproj at
Tulsi projects contain a few settings which control various behaviors during project generation and builds.
buildflags, customizable per compilation mode (
buildstartup flags, also customizable per compilation mode
fastbuild) used during project generation.
dbg, swap to
optif 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
Yesif 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.