|author||dierksen <email@example.com>||Mon Dec 10 12:34:27 2018 -0500|
|committer||Jonathan Dierksen <firstname.lastname@example.org>||Mon Dec 10 12:43:03 2018 -0500|
Update rules_apple dependency to version 0.10.0. - Also update the WORKSPACE rules to stuff that isn't broken. - Add a bazelrc for the common flags. - Remove the dmg target (requires disabling sandboxing anyway), so now `bazel build //...` works! Fixes #64 PiperOrigin-RevId: 224827343
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.