commit | 6a204bee40ada11f70c2c9865744dace29200450 | [log] [tgz] |
---|---|---|
author | Nicholas Levin <nglevin@vivarium.gs> | Wed Jul 25 16:28:01 2018 +0000 |
committer | Ivan Hernandez <ivanhernandez@google.com> | Fri Jul 27 22:07:33 2018 +0000 |
tree | 01015cc40c33ce48246ce27c21fe9cb2d1767328 | |
parent | 125aa37a8817e49651ebfc20df403747e9cf5ad0 [diff] |
Xcode 10 support This PR temporarily disables dark mode support for Xcode 10 until the views can be fully revised to support dark mode on Mojave, in a later Tulsi. This PR also removes the use of a range constructor that turns out to be wholly unnecessary, as the half open range operator already creates a Swift Range. It breaks the build in Xcode 10. That might have been an artifact in going from NSRanges to Swift Ranges in TulsiGenerator. Closes #53. PiperOrigin-RevId: 206004931
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:
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.