commit | 6a957cc6bf09a3fcf918039f779e02eda2eec10c | [log] [tgz] |
---|---|---|
author | davg <davg@google.com> | Fri Sep 21 08:17:16 2018 +0000 |
committer | Ivan Hernandez <ivanhernandez@google.com> | Thu Oct 04 14:55:33 2018 +0000 |
tree | c23e1083e48e3b9dfce510d8d2bb845d2134498c | |
parent | cf9245d332b3dc2917832d73de18c4d4f3a88906 [diff] |
Fixes for Xcode 10's new build system - Create a Run Script phase to write out dummy files for Objective-C sources in test targets. This silences some Xcode 10 warnings about .d files not being present, as well as issues with <target>_dependency_info.dat files. - Add the Xcode processed Info.plist file as an input to the bazel_build.py script to ensure it is processed before our script. This allows our script to safely overwrite it. PiperOrigin-RevId: 213950894
Open src/Tulsi.xcodeproj, and within Xcode, build the TulsiApp.
Run the TulsiApp.
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.