|author||Googler <firstname.lastname@example.org>||Tue Aug 27 20:06:52 2019 -0400|
|committer||kelvinchan-google <email@example.com>||Wed Aug 28 13:46:01 2019 -0400|
Skip creating indexer targets for targets that are direct dependencies of test targets. The way the xcode project is generated, all sources in targets that are direct dependencies of test targets are added into the Compile Sources phase of the test itself. So creating a separate indexer target for that file just means it will be indexed twice by Xcode, when it really doesn't need to be. PiperOrigin-RevId: 265800475
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.