commit | 0ff596d43a081b7571ddca9fb8f520c1c3c0dd09 | [log] [tgz] |
---|---|---|
author | Ravi Mandala <rmandala@linkedin.com> | Thu Jan 17 11:49:48 2019 -0500 |
committer | Jonathan Dierksen <dierksen@google.com> | Thu Jan 17 13:08:22 2019 -0500 |
tree | f1c3b150d000c6b0617325e1917dfc323f857860 | |
parent | 19dbbb2ceedb266d74a60dfe0809e403d81b76f6 [diff] |
Bugfix and tests: otherCFlags should not discard duplicate flags The otherCFlags param is a NSMutableOrderedSet while it should be NSMutableArray so that it does not mistakenly discard flags considering them duplicates. Also added a Test for the same Refer to issue: https://github.com/bazelbuild/tulsi/issues/75 \cc @DavidGoldman @reinhillmann @dierksen @ob Change-Id: Ie2aef33fc54a0889e7a361b11076ecedb87e8b11 Closes #76. PiperOrigin-RevId: 229754969
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.