| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
--
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows using compilers downloaded in *_repository rules without
ugly hacks like symlinks to bazel-out/../../external.
I manually tested all of the %prefix%s which this refactors the
implementations of.
--
Change-Id: Ie9931dfbed646b8b5c9cd7fba5e6df5cf0baa1f2
Reviewed-on: https://bazel-review.googlesource.com/#/c/2200
MOS_MIGRATED_REVID=108139097
|
|
|
|
|
|
|
|
|
|
|
|
| |
options. If a rule (such as a filegroup) doesn't
have C++ options in its transitive closure, then
buildOptions.get(CppOptions.class) returns null
and crashes.
So add a check to just fast-return for these cases.
--
MOS_MIGRATED_REVID=108079561
|
|
|
|
|
|
|
| |
as a quote separated list and DensitySpecificResourceFilter missing some densities.
--
MOS_MIGRATED_REVID=108077692
|
|
|
|
|
|
|
|
|
| |
label-based loading machinery) when the containing file is in a subdirectory of a package.
Also, while we're in the neighborhood: correct two nearby tests of relative loads that were passing for the wrong reasons.
--
MOS_MIGRATED_REVID=108072189
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108069029
|
|
|
|
|
|
|
|
|
|
|
| |
in ConfiguredTargetFunction.trimConfigurations to preserve
key insertion order.
This ensures that RuleContext.getPrerequisites returns an
attribute's deps in the same order they were declared.
--
MOS_MIGRATED_REVID=108063142
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than retrieve and process the reverse deps of an invalidated
node one at a time, batch request the set of reverse deps and then
process each of them.
This reduces the overhead of requesting values from the graph.
--
MOS_MIGRATED_REVID=108062933
|
|
|
|
|
|
|
| |
This makes query output independent of the insertion order of the dictionary.
--
MOS_MIGRATED_REVID=108061190
|
|
|
|
|
|
|
|
|
|
| |
Also introduces DottedVersion, a way to parse, represent and most of all compare
Apple's version identifiers.
RELNOTES: iOS apps and extensions now have launch_storyboard
--
MOS_MIGRATED_REVID=108060328
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108057030
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108056940
|
|
|
|
|
|
|
|
|
| |
attribute of the same name.
RELNOTES: Remove obsolete --objc_per_proto_includes flag.
--
MOS_MIGRATED_REVID=108056207
|
|
|
|
|
|
|
| |
FileSystemValueChecker when checking for dirty actions.
--
MOS_MIGRATED_REVID=108046467
|
|
|
|
|
|
|
|
|
|
| |
The thread that succeeds at marking a node dirty during invalidation
must then schedule that node's reverse deps for invalidation. Providing
the set of reverse deps as a return value from marking a node dirty
makes some future optimizations possible.
--
MOS_MIGRATED_REVID=108045473
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
include Skylark-declared requirements (which use names instead of fragment
class, e.g. "cpp" vs. CppConfiguration.class).
Also add "cpp" to Skylark java_* definitions, since java_* rules are
used to trigger LipoDataTransitions and thus expected to have a
CppConfiguration fragment.
Test coverage: skylark.BindTest with --experimental_dynamic_configs=1.
(and other Skylark tests).
--
MOS_MIGRATED_REVID=108041244
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108026192
|
|
|
|
|
|
|
| |
documentation.
--
MOS_MIGRATED_REVID=108019887
|
|
|
|
|
|
|
| |
A prerequisite is to pass RuleContext to ConfiguredAspect, so we can read from it the registered actions when we build() the aspect.
--
MOS_MIGRATED_REVID=107997593
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107989708
|