commit | 030c0ee9c8be6a1990058fd3052257e7cdc64f76 | [log] [tgz] |
---|---|---|
author | ivanhernandez <ivanhernandez@google.com> | Thu Aug 22 14:53:43 2019 -0400 |
committer | Rein Hillmann <rein@google.com> | Thu Aug 22 20:54:39 2019 -0400 |
tree | b266985d05ead31973c69859eab87875a70dca6b | |
parent | 6928bd74b6803da7b9856f4ed63760eebe14fc06 [diff] |
Always build both armv7k and arm64_32 architectures when targeting a physical watchOS device or building an application for a physical iOS device that also includes a watch app. When you build a watchOS target, Xcode does not provide a way to definitively determine the architecture of a connected watchOS device during the run script phase like it does for iOS devices (via the ARCHS environment variable) so we can't know which architecture to target when performing our bazel build. To ensure we always have the proper application architecture that needs to be deployed, always build a fat binary that includes the slices for both archs. Also removes alternate "Building for Apple Watch Series 4" option that is now unnecessary since we're always building for it. PiperOrigin-RevId: 264886356
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:
bazel
invocations, 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.py
script which is located in the generated xcodeproj at <xcodeproj>/.tulsi/Scripts/user_build.py
.Tulsi projects contain a few settings which control various behaviors during project generation and builds.
build
flags, customizable per compilation mode (dbg
and opt
)build
startup flags, also customizable per compilation modedbg
or opt
, no fastbuild
) used during project generation.dbg
, swap to opt
if 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 Yes
if 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.