| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 187218309
|
|
|
|
| |
PiperOrigin-RevId: 187218260
|
|
|
|
|
|
|
|
|
|
|
| |
Tests by running Bazel commands in the current working directory.
Change-Id: I0352e206a57e677b1c87e1c842a62ca1d3558bc3
Closes #4729.
Change-Id: Ib44810ebce596e4d40786e087f57e61971e87d25
PiperOrigin-RevId: 187214804
|
|
|
|
| |
PiperOrigin-RevId: 187212799
|
|
|
|
| |
PiperOrigin-RevId: 187212436
|
|
|
|
| |
PiperOrigin-RevId: 187209783
|
|
|
|
|
|
|
|
|
| |
This is only used by the static method of the same name, which is only used by RuleFactory.
This method is showing up in profiles as creating more garbage than I'm happy with, but not
enough to make me drop everything and fix it now. Instead make it private so folks are less
inclined to use it later...
PiperOrigin-RevId: 187208467
|
|
|
|
| |
PiperOrigin-RevId: 187199625
|
|
|
|
|
|
|
|
| |
Avoid throwing an execption if we don't have to, stack traces are expensive to
fill in.
RELNOTES: None
PiperOrigin-RevId: 187199392
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Use the path that contains a temporary junction in
the scope of the `with` statement that manages the
lifetime of the temp junction.
This allows compiling
//examples/android/java/bazel:hello_world again.
PiperOrigin-RevId: 187188442
|
|
|
|
|
|
|
|
|
| |
case where a pattern like '*.blah' doesn't match all the dirents.
Before the recent Path.java rewrite, the unconditional allocation here was free/amortized (in the sense that if Blaze ever had to consider the path in question, then we'd be doing the Path allocation anyway and caching the object). But now it's potentially GC churny, especially in the case where a single BUILD file has multiple glob expressions.
RELNOTES: None
PiperOrigin-RevId: 187185573
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187185374
|
|
|
|
|
|
| |
This flag changes the behavior of objc_library module map propagation so that module maps are only propagated to direct dependents, not transitive dependents. swift_library targets that import Objective-C code must then list those dependencies directly in its deps instead of depending on them being transitively present.
PiperOrigin-RevId: 187184692
|
|
|
|
|
|
|
|
| |
This requires codecs for CustomCommandLine and a Marshaller for Charset.
Added AutoCodec functionality to generic classes like Iterable<T>.
PiperOrigin-RevId: 187182889
|
|
|
|
|
|
|
| |
Progress on #4544.
RELNOTES: None.
PiperOrigin-RevId: 187179454
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
autogenerated cc toolchain
Relevant to #4031, fixes #4524.
Does not affect the osx + xcode toolchain that supports both C++ and ObjC!
RELNOTES: BAZEL_LINKOPTS is now consulted when autoconfiguring c++ toolchain
Now linker flags for the autogenerated C++ toolchain can be controlled by
BAZEL_LINKOPTS environment variable (using colon as a flag separator):
BAZEL_LINKOPTS=-lc++ bazel build //...
The default value is "-lstdc++:-lm".
PiperOrigin-RevId: 187173297
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make the --experimental_repository_cache option no longer experimental and enable
the cache by default. The default location is in the a separate directory under the
install base (under .cache/bazel user's home directory); this means it is shared
between workspaces und not between different versions of bazel. We plan to also
share it between different bazel versions in the future.
Fixes #4676.
RELNOTES:
repository_cache is no longer experimental and enabled by default.
Change-Id: I8499c2d1811e0fe8d830796e07cd6f8bc75e48ba
PiperOrigin-RevId: 187172766
|
|
|
|
|
|
|
|
| |
This function allows us to split strings coming from env variables into lists
while respecting %-escaping.
RELNOTES: None.
PiperOrigin-RevId: 187166226
|
|
|
|
|
|
|
|
|
|
|
| |
...so that it can use that path to compute other directories in the
output user base, in particular the default location for caches.
The first cache we will add is the hash-index cache for downloads
of external archives, but a spawn cache might be added later in the
output user base as well.
Change-Id: I24b1c33235c8f76ec008ecb1789163de2b2a45be
PiperOrigin-RevId: 187164275
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unknown commit fixes the only related broken target showing up in a TGP after
this change. It seems that this provider was only ever used through
java_wrap_cc with java_library dependencies which themselves had cc_library
dependencies, i.e. java_wrap_cc -> java_library -> cc_library. This dependency
is not needed, the cc_library can be added directly to java_wrap_cc to get the
same behavior and this is the way it should be done instead of relying on
transitive dependencies.
The reason for making this change right now is that with the Skylark C++ API, I
will be adding attr("deps").mandatoryProviders(CcCompilationInfo,
CcLinkParamsInfo) to C++ rules so that they can take any Skylark rule and not
having to explicitly hard-code the name of those Skylark rules in Blaze.
However, Java meets this criteria and the change would allow C++ rules to
depend on Java. This is not something that was supported before and is not
something we plan to support.
RELNOTES:none
PiperOrigin-RevId: 187158176
|
|
|
|
|
|
|
|
|
|
| |
`std::to_string` is faster than `std::stringstream`.
This issue only presents in older versions of Mingw/Cygwin. My Mingw64 GCC 7.1.0 has `std::to_string`. I can't determine the exact version of GCC that fixed the issue.
Closes #4493.
PiperOrigin-RevId: 187145391
|
|
|
|
| |
PiperOrigin-RevId: 187113491
|
|
|
|
|
|
|
| |
will be used for the dependency checker later. Refactoring it now just avoids future potential merge conflicts.
RELNOTES: None
PiperOrigin-RevId: 187103807
|
|
|
|
|
|
| |
come from Skylark, so we shouldn't crash. As a safety measure, subclasses of ActionLookupValue are now responsible for detecting action conflicts themselves.
PiperOrigin-RevId: 187095271
|
|
|
|
|
|
|
| |
import_deps_checker.
RELNOTES: None
PiperOrigin-RevId: 187095109
|
|
|
|
|
|
|
| |
:packages and checked-in gRPC jars.
RELNOTES: None
PiperOrigin-RevId: 187088590
|
|
|
|
|
|
|
|
| |
flags by it.
RELNOTES: None.
PiperOrigin-RevId: 187075897
|
|
|
|
|
|
|
|
|
|
| |
I'm assuming most of the time folks are only assigning one variable, which
doesn't require an ImmutableSet.Builder and the garbage it comes with.
Also took the liberty of removing some unused InterruptedException
declarations.
PiperOrigin-RevId: 187068400
|
|
|
|
|
|
| |
that has a single static INSTANCE field pointing back to the target field, so that serialization can grab it.
PiperOrigin-RevId: 187065629
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Only check/update type if the types of elements that we're adding changes. In
particular, the "is DICT/LIST" check can get expensive when run on every single
inserted element.
According to a hacky unit test (create 10M element SkylarkNestedSet 10x over) this is ~60%
faster (~18s -> ~7s).
This change is intended to be a quick fix, there's surely a more principled way
to make skylark's type checking more efficient...
PiperOrigin-RevId: 187062547
|
|
|
|
| |
PiperOrigin-RevId: 187059719
|
|
|
|
|
|
| |
evaluators that do not store errors alongside values, but which still support error transience.
PiperOrigin-RevId: 187058808
|
|
|
|
| |
PiperOrigin-RevId: 187057628
|
|
|
|
| |
PiperOrigin-RevId: 187057332
|
|
|
|
| |
PiperOrigin-RevId: 187054284
|
|
|
|
|
|
| |
This field is needed by the Android Studio with Bazel plugin.
PiperOrigin-RevId: 187053906
|
|
|
|
|
|
|
|
|
|
| |
AutoCodec still cannnot handle types with generic elements, e.g.
class Foo<T> {
private T member;
}
PiperOrigin-RevId: 187052487
|
|
|
|
|
|
|
| |
This zip is the input to the resource shrinker, which currently sometimes chokes on databinding expressions. This should fix that.
RELNOTES: None
PiperOrigin-RevId: 187049578
|
|
|
|
| |
PiperOrigin-RevId: 187048921
|
|
|
|
| |
PiperOrigin-RevId: 187044297
|
|
|
|
| |
PiperOrigin-RevId: 187043046
|
|
|
|
|
|
| |
class in https://github.com/bazelbuild/bazel/commit/14e549cc6596f67ed22c1bac0819f0775e4fb806).
PiperOrigin-RevId: 187042482
|
|
|
|
| |
PiperOrigin-RevId: 187038647
|
|
|
|
|
|
| |
Most of the time there's only one, doesn't justify the iterator overhead.
PiperOrigin-RevId: 187031802
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement the foundation of the C++ runfiles
library, along with a directory-based Runfiles
implementation.
Subsequent commits will add more feataures:
- manifest-based runfiles handling
- creating list of envvars to pass to child
processes
- automatic Runfiles creation based on argv[0] and
the envvars of this process
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: Id5a38619a1ae874499f04523863081559360410c
PiperOrigin-RevId: 187031518
|
|
|
|
|
|
|
|
|
|
|
| |
While rules that want to be called from different repositories may not
make any assumptions about locations of their dependencies, they still
may embed path obtained via expansion of $(location ...) into their files,
even if the dependencies refer to a different repository.
Add tests verifying that this behavior is preserved.
Change-Id: I2ee6cc806e30b6e18fad9b488012169da400895b
PiperOrigin-RevId: 187030372
|
|
|
|
| |
PiperOrigin-RevId: 187030267
|
|
|
|
|
|
|
|
|
|
|
| |
This cl introduces a bazel option
(--experimental_fix_linkstamp_inputs_bug_73447914) to control which inputs get
added into C++ linkstamp compile action. When set to true (defaults to false),
all inputs of relevant C++ linking action get added as inputs to the linkstamp
compile action too.
RELNOTES: None.
PiperOrigin-RevId: 187030217
|
|
|
|
| |
PiperOrigin-RevId: 187029559
|