| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
"bin"/"genfiles" instead of the default ones)
--
MOS_MIGRATED_REVID=108699595
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108691743
|
|
|
|
|
|
|
| |
RepositoryValue and not depending it from repository functions.
--
MOS_MIGRATED_REVID=108685867
|
|
|
|
|
|
|
|
|
|
| |
This is necessary to be able to verify that the network sandbox is
active using ifconfig, for example.
--
Change-Id: Ia3ea16e18cf1d280f31870c867e56336bb48e7bd
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/2361
MOS_MIGRATED_REVID=108685498
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108659943
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108645176
|
|
|
|
|
|
|
| |
Reduces garbage.
--
MOS_MIGRATED_REVID=108641543
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108626077
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108622328
|
|
|
|
|
|
|
| |
Reduces the amount of work needed when interruptibility isn't needed.
--
MOS_MIGRATED_REVID=108611609
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108592613
|
|
|
|
|
|
|
| |
Reduces garbage and wasted work
--
MOS_MIGRATED_REVID=108566164
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108555227
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108532339
|
|
|
|
|
|
|
| |
Reduces garbage generated during array resizing.
--
MOS_MIGRATED_REVID=108528430
|
|
|
|
|
|
|
| |
isolated from implementation details.
--
MOS_MIGRATED_REVID=108523104
|
|
|
|
|
|
|
| |
With the new-ish behavior of change pruning, where nodes transition from NEEDS_REBUILDING to REBUILDING, we need to make that transition unconditionally for dirty nodes -- being ready after unfinished deps were removed is irrelevant.
--
MOS_MIGRATED_REVID=108508979
|
|
|
|
|
|
|
|
|
| |
aapt requires this.
Also eliminate a few places where the unchecked RuleConfigurationException is thrown.
--
MOS_MIGRATED_REVID=108491660
|
|
|
|
|
|
|
|
|
|
|
|
| |
need the C++ fragment.
This option, specifically, requires special processing
because it's declared in BuildConfiguration.Options but
its "real" value is determined in CppConfiguration after
reading a CROSSTOOL.
--
MOS_MIGRATED_REVID=108394235
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108386134
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108376750
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108368348
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/634
MOS_MIGRATED_REVID=108365288
|
|
|
|
|
|
|
|
|
| |
target pattern.
Apart from the tests, I also tested this manually running "bazel query //..." in a tree with convenience symlinks.
--
MOS_MIGRATED_REVID=108325454
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108324961
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108282005
|
|
|
|
| |
MOS_MIGRATED_REVID=108278075
|
|
|
|
|
|
|
| |
dynamic config / configurable attributes change.
--
MOS_MIGRATED_REVID=108274420
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Specifically, given:
config_setting(
name = 'foo',
values = {'copts': '-DABC'})
this requires a dependency on the Cpp configuration fragment.
config_setting rules are unique in that this dependency comes
from string representations of option names.
--
MOS_MIGRATED_REVID=108268831
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108266475
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108258054
|
|
|
|
|
|
|
|
|
|
|
| |
If --output_groups is specified without a + or a - sign, it removes the
default output groups used for artifact selection from targets.
* Use output_groups=+<group_name> to add an output group,
* Use output_groups=-<group_name> to remove an output group.
--
MOS_MIGRATED_REVID=108247894
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108243881
|
|
|
|
|
|
|
| |
of recording VFS_ stats we try to catalog the access base on the path type.
--
MOS_MIGRATED_REVID=108238357
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the feature-based flags for links of native code for Android
were coming from the standard TARGET toolchain, which is wrong. This
went unnoticed because Bazel's CROSSTOOL (and mine until recently) don't
add any flags that way in either, which means getting the flags either
way results in none.
--
Change-Id: I74cd18ff56e3aea7ca61fabe62cb2246100ee59a
Reviewed-on: https://bazel-review.googlesource.com/#/c/2322
MOS_MIGRATED_REVID=108234274
|
|
|
|
|
|
|
| |
for the purpose of change pruning.
--
MOS_MIGRATED_REVID=108203369
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108186573
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108182745
|
|
|
|
|
|
|
|
|
| |
neverlink attribute.
RELNOTES: Resources defined locally on an android_library rule will respect the neverlink attribute.
--
MOS_MIGRATED_REVID=108178381
|
|
|
|
|
|
|
|
|
| |
This boolean matches bazel's semantics on whether a R.java class should
be generated. Android Studio generates its own in-memory class, but we
need to know *whether* we should generate one.
--
MOS_MIGRATED_REVID=108175802
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108174404
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as its input.
e.g. given input {"attr": [':a', ':b']}
the trimmed version also keeps ':a' in front of ':b'.
This preserves the expected invariant that prerequisites are
navigatable in BUILD declaration order.
--
MOS_MIGRATED_REVID=108170921
|
|
|
|
|
|
|
|
|
|
|
| |
an earlier version at which the child changed but the parent did not.
Concrete scenario: Parent depends on Child. We first evaluate at version v1, Child has value A1, Parent has value B1. We then evaluate at version v2, which changes a dependency of Child. Child has value A2, and Child.getVersion() returns v2. Parent re-evaluates to B1, so is unchanged. Parent.getVersion() returns v1. Now evaluate at version v3, which also changes a dependency of Child. Child re-evaluates to A2, so Child.getVersion() returns v2. If we signal Parent with v2 and Parent only knows that it is at version v1, then Parent must unnecessarily re-evaluate. To fix this, we store an additional version in the entry -- the version at which the node was last evaluated, even if the evaluation did not result in a new value. Parent can then compare that version to its children's versions. If that version is at least as recent as their versions, it knows that the result of evaluating will be the same as it was at that last evaluated version, which is its current value.
An alternative solution might be to just signal the parent with a boolean, saying whether or not the child was changed on this evaluation. However, this would be incorrect in the scenario above, with the modification that in the second evaluation, the user just requests the value of Child -- Parent is not updated. In that case, during the third evaluation, Child would report that it was not changed during this evaluation, but we must still re-evaluate Parent since it has not yet picked up the value of Child from the earlier build.
--
MOS_MIGRATED_REVID=108163443
|
|
|
|
|
|
|
|
|
| |
(accidentally) the implicit requirement that the deriving class override FileSystem#stat.
Even though this wasn't a problem in practice in the Bazel codebase (since all of our transitive subclasses had custom 'stat' implementation), it's good hygiene to have things correct (e.g. if we added a new subclass).
--
MOS_MIGRATED_REVID=108158039
|
|
|
|
|
|
|
| |
make sure that we don't store duplicate elements within a given group (although that is currently taken care of by the callers).
--
MOS_MIGRATED_REVID=108155105
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108154410
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108154189
|
|
|
|
|
|
|
| |
pretty simple: It aggregates up to 10k elements and then it notifies the parent.
--
MOS_MIGRATED_REVID=108144202
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108142409
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108142169
|