|author||Googler <email@example.com>||Tue Oct 08 17:56:47 2019 +0000|
|committer||Ivan Hernandez <firstname.lastname@example.org>||Thu Oct 10 01:11:53 2019 +0000|
Do not assume that CopyOnWrite arguments reside on the root filesystem. We can only do a CoW if the source and destination paths are on the same APFS volume. Checking that the root volume is APFS is not sufficient. TESTED=Manual testing on a MacBook with an APFS root volume and a FUSE mount; we cannot easily automate a test since we can't assume the types and mount points of filesystems on our automated test machines. PiperOrigin-RevId: 273558974
.bazelrcto see if the Xcode version used by Tulsi is installed locally. If it isn't, feel free to remove the
--xcode_versionflag or modify it as you wish, but note that Tulsi may not build correctly with different versions of Xcode.
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.