tree e4f1a840071122da11f92b60fbdc383ca1fc7aec
parent 07db4900490c46d9d9c51227924fa1f71856adcf
author davg <davg@google.com> 1531772798 -0400
committer Jonathan Dierksen <dierksen@google.com> 1531957383 -0400

Keep Bazel flags consistent

Whenever a Bazel configuration flag (i.e. --define, --copt) is
changed/added/removed, Bazel must reanalyze the entire build
graph (at least at the moment), which can be expensive.

In order to avoid doing so, we must keep all of the
analysis-cache-affecting flags used during the project generation
phase the same as the flags used during a build inside of Xcode.

There are a few keys points here:
- Make sure all of our Bazel invocations set the --override_repository
  flag and don't change its value between builds and generation
- We use different flags for Swift/non-Swift targets, so we have
  introduced a project-level which specifices which configuration
  flags to use during generation (Swift or non-Swift)
- User builds (from the command line) also follow the same
  restrictions; in order to make it easier for the user, we now have
  a script located inside the generated xcodeproj which allows
  building of a target with the same flags that Tulsi would use.

PiperOrigin-RevId: 204796256