|author||kaipi <firstname.lastname@example.org>||Thu Jan 10 21:34:14 2019 +0000|
|committer||Ivan Hernandez <email@example.com>||Thu Jan 10 23:40:20 2019 +0000|
Chmod tree artifact output to allow Xcode to write into it. When copying a tree artifact output from Bazel's output directory, it comes with Bazel's permissions, which are readonly. By adding +w to the attributes of the copied bundle, Tulsi allows Xcode to modify the output bundle, for example, for codesigning and injecting IDE specific dylibs. PiperOrigin-RevId: 228767293
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.