|author||hlopko <email@example.com>||Thu May 09 11:33:30 2019 -0400|
|committer||David Goldman <firstname.lastname@example.org>||Fri May 17 10:43:07 2019 -0400|
Add ctx argument to cc_common.configure_features In order to migrate C++ rules to platforms, we need the access to the C++ configuration fragment in Starlark APIs. All existing APIs have already access to it, but cc_common.configure_features doesn't. This change adds a ctx argument to configure_features. This is the migration needed for https://github.com/bazelbuild/bazel/issues/7793, and is part of the effort for https://github.com/bazelbuild/bazel/issues/6516. If the rule doesn't depend on cpp fragment yet, you will have to add `fragments =['cpp']` argument to the rule() call. Note that this behavior is only available in Bazel 0.25 (to be released this month). PiperOrigin-RevId: 247430782
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.