|author||ivanhernandez <email@example.com>||Fri Jun 26 10:05:16 2020 -0400|
|committer||David Goldman <firstname.lastname@example.org>||Mon Jun 29 15:52:46 2020 -0400|
Update Tulsi to Xcode 11.5. PiperOrigin-RevId: 318465055
build_and_run.sh. This will install Tulsi.app inside
$HOME/Applications by default. See below for supported options:
-b: Bazel binary that Tulsi should use to build and install the app (Default is
-d: The folder where to install the Tulsi app into (Default is
-x: The Xcode version Tulsi should be built for (Default is
Tulsi-generated Xcode projects use Bazel to build, not Xcode. Building in Xcode will cause it to only run a script; the script invokes Bazel to build the configured Bazel target and copies the artifacts to where Xcode expects them to be. 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.